From: Jeff Mickey <j@codemac.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: List of abbreviations for licenses
Date: Thu, 29 Nov 2012 15:53:40 -0800 [thread overview]
Message-ID: <CAKr=PyO1M2hFS-T9xhLadYOX=ZO+CHyqCs4SAKGCwBK2-FZvfQ@mail.gmail.com> (raw)
In-Reply-To: <87vcco2hgr.fsf@gnu.org>
On Thu, Nov 29, 2012 at 2:05 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> More importantly, licensing is not a science, and we can’t pretend to
> devise a universal “license calculus”. (This has been discussed at
> length in the past on nix-dev.)
>
> Thus, I would start with a simple (guix licenses) module. I would
> perhaps even omit the <license> type, and use just plain strings to
> start with.
>
> WDYT?
Unsolicited advice incoming..
Licenses are a huge pain when you get into all the custom ones out
there. This has also been discussed at length on arch-dev years ago.
IIRC ArchLinux uses an array of strings for each package, and then
when you build the package you get warnings about licenses that are
unique/new. You then add the LICENSE file to the package so the
warning goes away, and it gets placed in a common licenses directory.
I don't quite remember the mechanics of how it checked this, and I'm
sure it's changed by now.
I think the important part here is if you use strings, have some way
to check if someone is building a package with a new/undocumented
license. Then the graph of license objects could be accomplished
later, if you know you don't have misspellings like "LGLPv2" and stuff
like it polluting the graph.
// jeff
next prev parent reply other threads:[~2012-11-29 23:54 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 [this message]
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
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='CAKr=PyO1M2hFS-T9xhLadYOX=ZO+CHyqCs4SAKGCwBK2-FZvfQ@mail.gmail.com' \
--to=j@codemac.net \
--cc=bug-guix@gnu.org \
--cc=ludo@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).