all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Timothy Sample <samplet@ngyro.com>
Cc: 43014-done@debbugs.gnu.org
Subject: bug#43014: Install license files to all outputs
Date: Tue, 25 Aug 2020 10:05:16 +0300	[thread overview]
Message-ID: <20200825070516.GA979@E5400> (raw)
In-Reply-To: <87tuwrbed3.fsf@ngyro.com>

[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]

On Mon, Aug 24, 2020 at 11:20:40PM -0400, Timothy Sample wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
> 
> > Efraim Flashner <efraim@flashner.co.il> skribis:
> >
> >> It seems to me that the license file(s) should be installed to all the
> >> outputs.
> >
> > Isn’t it already happening, at least with ‘gnu-build-system’?
> >
> > [...]
> >
> > Perhaps there are corner cases or an issue specific to
> > ‘ghc-build-system’?
> 
> In the case of ‘git-annex’, it just needs a ‘license-file-regexp’
> argument, which is easy enough to fix.  For ‘scroll’, it’s missing a
> license file.  There is “GPL.hs”, but it doesn’t really count, IMO.  It
> contains the text of the GPL (version 2), but as a Haskell string.  I
> guess it’s better than nothing.
> 
> I think there is no bug here, just bad luck.  :)
> 
> 
> -- Tim

Works for me.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-08-25  7:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24  9:00 bug#43014: Install license files to all outputs Efraim Flashner
2020-08-24 21:17 ` Ludovic Courtès
2020-08-25  3:20   ` Timothy Sample
2020-08-25  7:05     ` Efraim Flashner [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

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

  git send-email \
    --in-reply-to=20200825070516.GA979@E5400 \
    --to=efraim@flashner.co.il \
    --cc=43014-done@debbugs.gnu.org \
    --cc=samplet@ngyro.com \
    /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.