unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Diego Nicola Barbato <dnbarbato@posteo.de>
Subject: Re: Packaging Inferno
Date: Mon, 8 Oct 2018 13:47:22 +0000	[thread overview]
Message-ID: <20181008134722.bulv4wn6up6dmvx2@abyayala> (raw)
In-Reply-To: <87bm841tlx.fsf@gnu.org>

Ludovic Courtès transcribed 1.9K bytes:
> Hello Diego,
> 
> Diego Nicola Barbato <dnbarbato@posteo.de> skribis:
> 
> > I have written a package definition for Inferno and I would like to know
> > if it would make sense to add it to Guix.  I am asking because I am not
> > sure if it is compatible with the FSDG (bundled fonts, trademarks, ...)
> > and if it would be of any use to anyone.
> 
> Removing the proprietary(?) fonts like you did sounds like the right
> thing to do.  As for trademarks, please see
> <https://www.gnu.org/distros/free-system-distribution-guidelines.html#trademarks>
> to determine whether there’s a problem at all.
> 
> Could you also check whether all the code is GPLv2+ like the ‘license’
> field suggests?
> 
> Do I get it right that the build result is a script that launches
> Inferno as a GNU/Linux process?  It seems like it could be useful.
> 
> Some comments about the package definition:
> 
> >     (build-system trivial-build-system)
> >     (native-inputs `(("bash" ,bash)
> >                      ("coreutils" ,coreutils)
> >                      ("grep" ,grep)
> >                      ("sed" ,sed)
> >                      ("awk" ,gawk)
> >                      ("xz" ,xz)
> >                      ("tar" ,tar)
> >                      ("gcc-toolchain" ,gcc-toolchain)                     ))
> >     (inputs `(("libx11" ,libx11)
> >               ("xorgproto" ,xorgproto)
> >               ("libxext" ,libxext)))
> 
> Like Efraim wrote, I think using ‘gnu-build-system’ would allow you to
> simplify the package definition.
> 
> >              ;; build mk
> >              (invoke "./makemk.sh")
> 
> It would be ideal if we had a separate package for ‘mk’ (I suppose it
> can run on POSIX systems, right?).

I can finish my mk package and send it in.
My mk is the canonical set of mk files as used by bmake.
Sources are from http://crufty.net/help/sjg/mk-files.htm
and/or places linked from there.

If this matches the mk mentioned here, I can create this patch.

> Once you’ve double-checked the licensing and trademark situation, I
> think you can go ahead and submit it as a patch (or two patches, with
> ‘mk’ separately).
> 
> Thanks!
> 
> Ludo’.
> 

  reply	other threads:[~2018-10-08 14:00 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 [this message]
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

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=20181008134722.bulv4wn6up6dmvx2@abyayala \
    --to=ng0@n0.is \
    --cc=dnbarbato@posteo.de \
    --cc=guix-devel@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).