unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 48810@debbugs.gnu.org
Subject: [bug#48810] [PATCH] gnu: Add matterbridge.
Date: Fri, 4 Jun 2021 18:16:02 +0200	[thread overview]
Message-ID: <20210604181602.0d04d3f5@primarylaptop.localdomain> (raw)
In-Reply-To: <87im2testl.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]

On Fri, 04 Jun 2021 14:07:50 +0200
Mathieu Othacehe <othacehe@gnu.org> wrote:

> Hello,
Hi,

> The linter reports two problems:
> 
> --8<---------------cut here---------------start------------->8---
> gnu/packages/messaging.scm:2977:5: matterbridge@1.22.2: the source
> file name should contain the package name
> gnu/packages/messaging.scm:2977:5: matterbridge@1.22.2: the source
> URI should not be an autogenerated tarball --8<---------------cut
> here---------------end--------------->8---
>
> which means that you should use:
> 
> > +      (method url-fetch)
> 
> git-fetch here,
> 
> > +      (sha256
> > +       (base32
> > +        "1p3mkfzv4xwm7vz8ja7qsa99qwxb9s61hnjjv65dkkjivlsif5hk"))))
> 
> and introduce something like:
> 
> --8<---------------cut here---------------start------------->8---
>        (file-name (git-file-name name version))
> --8<---------------cut here---------------end--------------->8---
Thanks a lot.

I've seen these warnings but I ignored thinking I couldn't fix it as I
didn't find any alternate files for the releases.

I've now sent an updated version.

By the way, I don't know much about go, and I'm pretty new to Guix, so
I did this package through trial and error and also looking at how
things were done in Parabola (through the Arch Linux Community
repository where the matterbridge package comes from).

And the Submitting Patches section of the manual[1] has the following:
> Make sure the package does not use bundled copies of software
> already available as separate packages. 

Here I'm unsure of what is being done under the hood, but at least
Parabola / Arch Linux don't seem to do anything special with that.

In any case I've already started deploying a matterbridge service by
using this package (with Guix pack) and a modified systemd service
file from Arch Linux on top of Trisquel 9 to bridge several IRC
channels, and so far it worked fine.

References:
-----------
[1]https://guix.gnu.org/manual/en/guix.html#Submitting-Patches 

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2021-06-04 16:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 13:22 [bug#48810] [PATCH] gnu: Add matterbridge Denis 'GNUtoo' Carikli
2021-06-04 12:07 ` Mathieu Othacehe
2021-06-04 16:11   ` [bug#48810] [PATCH v2] " Denis 'GNUtoo' Carikli
2021-06-06 16:34     ` bug#48810: " Mathieu Othacehe
2021-06-04 16:16   ` Denis 'GNUtoo' Carikli [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210604181602.0d04d3f5@primarylaptop.localdomain \
    --to=gnutoo@cyberdimension.org \
    --cc=48810@debbugs.gnu.org \
    --cc=othacehe@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).