all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add libiax
Date: Tue, 31 May 2016 17:02:42 -0400	[thread overview]
Message-ID: <20160531210242.GC19631@jasmine> (raw)
In-Reply-To: <20160531190221.GA21454@solar>

On Tue, May 31, 2016 at 09:02:21PM +0200, Andreas Enge wrote:
> Hello,
> 
> just a quick comment on the name:
> 
> On Mon, May 30, 2016 at 02:47:55PM -0500, Lukas Gradl wrote:
> > Upstream seems to refer to the software as "iax" "libiax" and "libiax2"
> > interchangeably.  The "2" was the closest thing I could find to a version
> > number.
> 
> notice that the tarball name is always "correct" as the package name, unless
> upstream consistently uses a different name. In this case:
> 
> +           "https://gitlab.savoirfairelinux.com/sflphone/libiax2/"
> +           "repository/archive.tar.gz?ref="
> 
> I would suggest to use "libiax2" as the package name (variable name and
> package NAME field), and the version number as proposed by Leo.

Okay, so let's change the naming to libiax2, and give some more detail
about the licensing, as shown in my patch from earlier today. Then we
should be ready to merge :)

  reply	other threads:[~2016-05-31 21:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-28 23:08 [PATCH] Add libiax Lukas Gradl
2016-05-29  0:48 ` Leo Famulari
2016-05-30 19:47   ` Lukas Gradl
2016-05-31 19:02     ` Andreas Enge
2016-05-31 21:02       ` Leo Famulari [this message]
2016-06-01 14:40         ` Lukas Gradl
2016-06-02  1:44           ` Leo Famulari
2016-05-29  0:55 ` Leo Famulari
2016-05-30 19:50   ` Lukas Gradl
2016-05-31 16:25     ` Leo Famulari
2016-05-31 17:40       ` Efraim Flashner
2016-05-31 19:13       ` Andreas Enge
2016-05-31 21:01         ` Leo Famulari
2016-05-31 20:59       ` Leo Famulari

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

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

  git send-email \
    --in-reply-to=20160531210242.GC19631@jasmine \
    --to=leo@famulari.name \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.