unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jeff Mickey <j@codemac.net>
Cc: bug-guix@gnu.org
Subject: Re: List of abbreviations for licenses
Date: Fri, 30 Nov 2012 01:49:56 +0100	[thread overview]
Message-ID: <87hao7zzgr.fsf@gnu.org> (raw)
In-Reply-To: <CAKr=PyO1M2hFS-T9xhLadYOX=ZO+CHyqCs4SAKGCwBK2-FZvfQ@mail.gmail.com> (Jeff Mickey's message of "Thu, 29 Nov 2012 15:53:40 -0800")

Hi,

Jeff Mickey <j@codemac.net> skribis:

> 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.

Right.  Referring to variables defined in (guix licenses) instead of
using plain strings directly should help with that.

Thanks,
Ludo’.

  reply	other threads:[~2012-11-30  0:50 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 [this message]
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=87hao7zzgr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=j@codemac.net \
    /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).