all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add awesome.
Date: Mon, 13 Jun 2016 22:12:16 -0400	[thread overview]
Message-ID: <20160614021216.GB16928@jasmine> (raw)
In-Reply-To: <CAFAGzb9gE2Ki3GKixmvg8q+2gG21CzQ+S5=+Equ46Oedjpfhxg@mail.gmail.com>

On Tue, Jun 14, 2016 at 10:57:41AM +1000, Carlo Zancanaro wrote:
> On 14 June 2016 at 01:46, Leo Famulari <leo@famulari.name> wrote:
> 
> > I think that imagemagick is only required while building, so it can be a
> > 'native-input'.
> >
> > You can check what packages the built output refers to: $ guix gc
> > --references $(./pre-inst-env guix build awesome)
> >
> > Imagemagick is not in the list.
> >
> 
> Thanks for this! I had assumed that the "guix lint" would tell me about
> something like that, given the check "inputs-should-be-native".
> 
> Is it possible for those references to be "wrong"? For there to be
> something which is required at runtime, but doesn't show up in a "guix gc
> --references" check?

My understanding is that `guix gc --references` reports the references
that it finds by scanning the store item you give as an argument (I
haven't read the code). So, if the packaged software needs to refer to
something but does not, you will not be warned by `guix gc --references`.

From ImageMagick, awesome uses the `convert` tool at build time. I
skimmed the results of `grep -r convert` and I didn't notice any other
uses of the tool, but I might have missed something. Can you
double-check?

> > I noticed that several of the files have the "or later" text. If they
> > are all like that, we could use gpl2+. Did you check if there are any
> > files with licenses besides GPL2+?
> >
> 
> The lua files (in lib/) don't have a license heading beyond a copyright
> year/author in the luadoc tags. Everything which has a license heading
> seems to be gpl2+ (I had missed the "or later" text, but I've updated it
> now).

Okay.

  reply	other threads:[~2016-06-14  2:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  0:12 [PATCH] gnu: Add awesome Carlo Zancanaro
2016-06-13  0:28 ` Carlo Zancanaro
2016-06-13  0:38 ` Carlo Zancanaro
2016-06-13  7:53   ` Danny Milosavljevic
2016-06-13 11:54     ` Carlo Zancanaro
2016-06-13 15:09       ` Ludovic Courtès
2016-06-13 15:46   ` Leo Famulari
2016-06-14  0:57     ` Carlo Zancanaro
2016-06-14  2:12       ` Leo Famulari [this message]
2016-06-14  2:16       ` Leo Famulari
2016-06-13  8:05 ` ng0
2016-06-13 12:01   ` Carlo Zancanaro
2016-06-15 12:15 ` Carlo Zancanaro
2016-06-16 12:38   ` Ludovic Courtès
2016-06-16 23:31     ` Carlo Zancanaro
2016-06-16 23:49       ` Leo Famulari
2016-07-31 21:45         ` ng0
2016-07-31 22:00           ` Leo Famulari

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160614021216.GB16928@jasmine \
    --to=leo@famulari.name \
    --cc=carlo@zancanaro.id.au \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.