From: Leo Famulari <leo@famulari.name>
To: Tobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add idle3-tools.
Date: Thu, 3 Mar 2016 23:33:56 -0500 [thread overview]
Message-ID: <20160304043356.GA3103@jasmine> (raw)
In-Reply-To: <CAKFHe2Q8wXanHUm9mWOGxjf=uo+piFyoXBj+XUpSbHBfks=7yQ@mail.gmail.com>
On Fri, Mar 04, 2016 at 04:22:36AM +0100, Tobias Geerinckx-Rice wrote:
> For example, I'm now no longer sure why I added a licence
> namespace nor whether that's a good idea.
I'm not sure either :)
There are licenses and packages both named 'expat' and 'openssl', so
when we need to use both the package and the license of one of those
names in a single module, we must prefix the license. Otherwise the
symbol is ambiguous and the module can't be built.
If that's not the case here, can you resubmit without the license
prefix?
>
> Now, if you'll excuse me, I need to throw a certain console
> browser out of a very high window.
>
> On 04/03/2016, Tobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com> wrote:
> > Hallo Guix,
> >
> > Perhaps I should have added that I did run `guix lint'
> > on this without issues.
> >
> > Anyone fancy having a look?
> >
> > T G-R
> >
>
next prev parent reply other threads:[~2016-03-04 4:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 3:56 Adding idle3-tools while unable to run ‘guix lint’ Tobias Geerinckx-Rice
2016-02-16 3:56 ` [PATCH] gnu: Add idle3-tools Tobias Geerinckx-Rice
2016-03-04 3:13 ` Tobias Geerinckx-Rice
2016-03-04 3:22 ` Tobias Geerinckx-Rice
2016-03-04 4:33 ` Leo Famulari [this message]
2016-03-08 0:47 ` [PATCH v2] " Tobias Geerinckx-Rice
2016-03-16 4:02 ` Tobias Geerinckx-Rice
2016-03-16 6:36 ` Leo Famulari
2016-03-16 21:44 ` Tobias Geerinckx-Rice
2016-02-16 7:26 ` Adding idle3-tools while unable to run ‘guix lint’ Pjotr Prins
2016-02-16 16:22 ` Tobias Geerinckx-Rice
2016-02-16 16:55 ` Tobias Geerinckx-Rice
2016-02-17 10:44 ` Ricardo Wurmus
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=20160304043356.GA3103@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=tobias.geerinckx.rice@gmail.com \
/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).