From: ludo@gnu.org (Ludovic Courtès)
To: Kete <kete@ninthfloor.org>
Cc: guix-devel@gnu.org
Subject: Re: Package Definition Place
Date: Sun, 05 Jan 2014 18:57:08 +0100 [thread overview]
Message-ID: <87ob3qb9cb.fsf@gnu.org> (raw)
In-Reply-To: <1435749.Bp1j5CarR9@knossos> (kete@ninthfloor.org's message of "Sat, 04 Jan 2014 16:31:08 -0500")
Kete <kete@ninthfloor.org> skribis:
> On Saturday, January 04, 2014 12:47:06 PM Ludovic Courtès wrote:
>> I’d recommend looking at how that tcsetpgrp check is implemented, to see
>> what makes it think it doesn’t work. In particular what does
>> ‘config.log’ report about this test?
>
> I didn't find any mention.
Hmm, that’s surprising. Normally config.log contains details about
failed configure tests.
>> The ‘license’ field should reflect the license of what gets installed.
>> So if build-time scripts are GPL, that doesn’t matter here. But please
>> do skim over the license headers to make sure they’re all under that
>> X11-style license.
>
> Here is what I found with grep:
> Completion/Unix/Command/_darcs is licensed under the GNU GPL. "zsh
> will be linked against libgdbm. This means the binary is covered by
> the GNU General Public License. This does not affect the source
> code." config.guess and config.sub are also GPLed.
Does it comes with a copy of GDBM? Or is it an optional dependency?
If the latter, then I guess you should add that dependency.
> The rest default to that X11-style license.
So you should keep that ‘x11-style’ license, with a comment above saying
that, since it’s linked against GDBM, it’s GPLv3+ in practice.
If it builds fine, feel free to post a patch as produced by ‘git
format-patch’ (please read “Submitting Patches” in ‘HACKING’.)
Thanks,
Ludo’.
prev parent reply other threads:[~2014-01-05 17:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 3:55 Package Definition Place Kete
2013-12-30 7:16 ` John Darrington
2013-12-31 0:37 ` Kete
2014-01-01 12:52 ` John Darrington
2014-01-01 16:05 ` Kete
[not found] ` <1458111.8sUPPTkUlg@knossos>
[not found] ` <20140101160917.GA13487@intra>
2014-01-01 16:32 ` Kete
2014-01-01 16:50 ` John Darrington
2014-01-01 19:13 ` Kete
2014-01-01 19:55 ` John Darrington
2014-01-01 20:38 ` Kete
2014-01-01 22:30 ` Kete
2014-01-02 2:44 ` Nikita Karetnikov
2014-01-02 2:50 ` Nikita Karetnikov
2014-01-02 10:06 ` Kete
2014-01-02 14:58 ` Nikita Karetnikov
2014-01-02 23:45 ` Kete
2014-01-03 2:28 ` Kete
2014-01-03 5:50 ` John Darrington
2014-01-03 11:37 ` Kete
2014-01-03 15:16 ` Nikita Karetnikov
2014-01-03 15:19 ` Ludovic Courtès
2014-01-04 1:10 ` Kete
2014-01-04 7:15 ` John Darrington
2014-01-04 21:21 ` Kete
2014-01-04 22:25 ` John Darrington
2014-01-05 18:21 ` Ludovic Courtès
2014-01-04 11:47 ` Ludovic Courtès
2014-01-04 21:31 ` Kete
2014-01-05 17:57 ` Ludovic Courtès [this message]
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=87ob3qb9cb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=kete@ninthfloor.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).