From: Nikita Karetnikov <nikita.karetnikov@gmail.com>
To: bug-guix@gnu.org
Subject: Re: List of abbreviations for licenses
Date: Sat, 8 Dec 2012 01:34:08 +0300 [thread overview]
Message-ID: <CAD15K4shLrDAjngKyuVt354UtcaKwMzQfdH5-4M3aWQqAtK5Pw@mail.gmail.com> (raw)
In-Reply-To: <87k3stprjs.fsf@gnu.org>
> Can you make this a single #:export?
Which one should I use? (The latter looks better, IMHO.)
#:export (license? license-name asl2.0 boost1.0 bsd-2 bsd-3 bsd-4
cddl1.0 cpl1.0 epl1.0 gpl2 gpl2+ gpl3 gpl3+ ijg ibmpl1.0 lgpl2.1
lgpl2.1+ lgpl3 lgpl3+ mpl2.0 openssl public-domain x11 zlib)
#:export (license? license-name
asl2.0
boost1.0
bsd-2 bsd-3 bsd-4
cddl1.0
cpl1.0
epl1.0
gpl2 gpl2+ gpl3 gpl3+
ijg
ibmpl1.0 lgpl2.1 lgpl2.1+ lgpl3 lgpl3+
mpl2.0
openssl
public-domain
x11
zlib)
> While we’re at it, we should add a ‘url’ field to <license>, so that the
> URL above would be a field of the license object instead of being a
> comment.
I think that we should use 'uri' instead. [1]
[1] https://upload.wikimedia.org/wikipedia/commons/c/c3/URI_Euler_Diagram_no_lone_URIs.svg
next prev parent reply other threads:[~2012-12-07 22:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 4:54 List of abbreviations for licenses Nikita Karetnikov
2012-11-29 22:05 ` Ludovic Courtès
2012-11-29 23:53 ` Jeff Mickey
2012-11-30 0:49 ` Ludovic Courtès
2012-12-06 22:52 ` Nikita Karetnikov
2012-12-07 9:43 ` Ludovic Courtès
2012-12-07 19:53 ` Ludovic Courtès
2012-12-07 22:34 ` Nikita Karetnikov [this message]
2012-12-07 23:24 ` Ludovic Courtès
2012-12-08 2:14 ` Nikita Karetnikov
2012-12-08 18:23 ` Ludovic Courtès
2012-12-09 2:47 ` Nikita Karetnikov
2012-12-09 13:41 ` Ludovic Courtès
2012-12-11 8:24 ` Nikita Karetnikov
2012-12-11 10:24 ` Ludovic Courtès
2012-12-11 14:04 ` Nikita Karetnikov
2012-12-11 14:31 ` Ludovic Courtès
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=CAD15K4shLrDAjngKyuVt354UtcaKwMzQfdH5-4M3aWQqAtK5Pw@mail.gmail.com \
--to=nikita.karetnikov@gmail.com \
--cc=bug-guix@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).