From: Chris Marusich <cmmarusich@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add sg3_utils.
Date: Sun, 14 Aug 2016 19:15:06 -0700 [thread overview]
Message-ID: <87d1lawzf9.fsf@gmail.com> (raw)
In-Reply-To: <20160814192155.GA3327@jasmine> (Leo Famulari's message of "Sun, 14 Aug 2016 15:21:55 -0400")
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
Leo Famulari <leo@famulari.name> writes:
> Generally, we have the problem of using different variables named
> 'expat', 'zlib', 'openssl', and possibly others. For those 3, there are
> both package and license variables sharing the name.
>
> So, if we want to refer to both the package and license variables of,
> for example, expat, we have to distinguish them somehow. So, we
> sometimes "prefix" the licenses when they are used, to distinguish them
> from the packages.
>
> There is a good example in 'gnu/packages/admin.scm'. Check line 33,
> where the license module is imported:
>
> 33 #:use-module ((guix licenses) #:prefix license:)
>
> and line 107, where you can see it in action:
>
> 107 (license license:gpl2+)))
>
> Using #:select to only import specific licenses can help, but you still
> have a problem when it's time to #:select the expat license.
I see! That's useful. Thanks for the tip.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-08-15 2:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 9:42 [PATCH] gnu: Add sg3_utils Chris Marusich
2016-08-13 9:52 ` Chris Marusich
2016-08-14 1:27 ` Leo Famulari
2016-08-14 3:23 ` Chris Marusich
2016-08-14 16:46 ` Leo Famulari
2016-08-14 18:49 ` Chris Marusich
2016-08-14 19:21 ` Leo Famulari
2016-08-15 2:15 ` Chris Marusich [this message]
2016-08-14 1:17 ` 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=87d1lawzf9.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.