From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Adrien 'neox' Bourmault <neox@gnu.org>, help-guix@gnu.org
Subject: Re: License compliance when redistributing images built with 'guix system'.
Date: Mon, 18 Nov 2024 13:38:43 +0100 [thread overview]
Message-ID: <20241118133843.2f1787b7@primary_laptop> (raw)
In-Reply-To: <20241118094141.44e5487c@primary_laptop>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
On Mon, 18 Nov 2024 09:41:41 +0100
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:
> But now I have another problem: some of the paths don't exist. For
> instance the code above lists
> /gnu/[...]-ath9k-htc-firmware-1.4.0-checkout which doesn't exist.
I've found an idea for working around that: I can get the file name and
loop over all the packages, match a package's origin-actual-file-name
against the name above, and once we have the package we can simply run
guix build --sources=transitive with it.
I'll report if it works or not.
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-18 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 0:09 License compliance when redistributing images built with 'guix system' Denis 'GNUtoo' Carikli
2024-07-17 17:26 ` Simon Tournier
2024-07-28 17:20 ` Denis 'GNUtoo' Carikli
2024-09-30 20:11 ` Denis 'GNUtoo' Carikli
2024-11-18 8:41 ` Denis 'GNUtoo' Carikli
2024-11-18 12:38 ` Denis 'GNUtoo' Carikli [this message]
2024-11-22 23:56 ` Denis 'GNUtoo' Carikli
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=20241118133843.2f1787b7@primary_laptop \
--to=gnutoo@cyberdimension.org \
--cc=help-guix@gnu.org \
--cc=neox@gnu.org \
--cc=zimon.toutoune@gmail.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.
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).