From: ludo@gnu.org (Ludovic Courtès)
To: Diego Nicola Barbato <dnbarbato@posteo.de>
Cc: guix-devel@gnu.org
Subject: Re: Packaging Inferno
Date: Wed, 24 Oct 2018 14:58:59 +0200 [thread overview]
Message-ID: <87tvlb4i24.fsf@gnu.org> (raw)
In-Reply-To: <87o9bnien7.fsf@GlaDOS.home> (Diego Nicola Barbato's message of "Sun, 21 Oct 2018 15:59:56 +0200")
Hi Diego,
Diego Nicola Barbato <dnbarbato@posteo.de> skribis:
> I have sent a patch incorporating most of your feedback to
> guix-patches@gnu.org (bug#33080).
Thank you, and sorry that review takes some time. I guess that’s the
price to pay when submitting non-trivial packages. ;-)
>> Do you know whether other FSDG distros and Debian provide these fonts?
>
> They do not provide these exact fonts but those from which some of these
> are derived (misc and jis are "based" on X fonts, vera is probably based
> on Bitstream Vera).
> It is harder to find the origin of the other fonts as there is little
> information about them (big5 was "provided by students at the University
> of Hong Kong" according to its README; courier, gb, and minitel do not
> contain any information). The remaining fonts just reuse "subfonts"
> from the other directories.
OK. Courier is a standard PostScript font (with a free implementation
by the URW++ foundry), so it’s probably fine. I don’t know about the
others; it’s probably safe, but perhaps you could ask for advice on the
GNU/Linux-libre mailing list? (See
<https://lists.nongnu.org/mailman/listinfo/gnu-linux-libre>.)
>> Note that the page above says that the Lucent PL is incompatible with
>> the GPL. Are we combining GPL code with Lucent code here?
>
> AFAICT LPL code (libmp libsec) is combined with GPL code when building
> emu. There is some more LPL code in the os directory, which is only
> needed for building native inferno, and in the appl and module
> directories, which contain Limbo code which is run on inferno but not
> used to build it.
> The NOTICE says that all licenses are compatible with the GPLv2 but that
> is apparently incorrect.
> As I am not very familiar with software licenses I do not know what to
> do about this. According to the GPL FAQ [*] it is possible to add an
> exception when using incompatible libraries, but I am hesitant to
> suggest this in a bug report to upstream because I do not know if that
> applies here.
>
> Is this a blocker?
What you’re writing about libmp/libsec linked into ‘emu’ sounds like it
could be a GPL violation. Again, to be sure, I’d suggest getting
feedback from the GNU/Linux-libre mailing list (in a separate thread.)
>> Sounds good. Note that, if possible, we should stick to the usual file
>> system layout (that is OUT/share, OUT/lib, OUT/bin, etc. and not
>> OUT/usr.) Though if keeping the /usr/inferno layout style is really
>> important, we can make an exception.
>
> The layout style is not important; I only used OUT/usr/inferno because
> /usr/inferno is the default in mkconfig. I have changed this to
> OUT/share/inferno, which matches what the Nix package [†] does.
Sounds good.
Thank you!
Ludo’.
prev parent reply other threads:[~2018-10-24 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 8:11 Packaging Inferno Diego Nicola Barbato
2018-10-07 9:49 ` Efraim Flashner
2018-10-11 13:30 ` Diego Nicola Barbato
2018-10-11 13:44 ` Efraim Flashner
2018-10-08 13:00 ` Ludovic Courtès
2018-10-08 13:47 ` Nils Gillmann
2018-10-09 17:09 ` Diego Nicola Barbato
2018-10-09 17:55 ` Nils Gillmann
2018-10-17 17:35 ` Diego Nicola Barbato
2018-10-16 12:03 ` Ludovic Courtès
2018-10-21 13:59 ` Diego Nicola Barbato
2018-10-24 12:58 ` 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=87tvlb4i24.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dnbarbato@posteo.de \
--cc=guix-devel@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).