From: Andy Tai <atai@atai.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: guix pack on Linux kernel
Date: Sun, 25 Jul 2021 16:16:51 -0700 [thread overview]
Message-ID: <CAJsg1E-U9cW_Pdx-5t3r1ODxFJ3-nCu+tecDeY-hYVn2N+QjHA@mail.gmail.com> (raw)
In-Reply-To: <878s1v4c4l.fsf@elephly.net>
sorry for the series of questions, but a follow on question:
If I create and distribute such a guix pack bundle, is there an easy
way to create a tar.gz file containing the sources to fit GPL
requirements? I assume now there is no guix command to create a
"source pack" for a guix pack. Even if there is, can a tar.gz of the
directories of the sources be enough to re-create the binary pack?
Or basically the user shall have the full guix git repo built locally,
plus the sources of the programs bundled, before he or she can
re-create the guix pack.
Question is essentially how to meet GPL requirements (user given the
sources to be able to recreate the binaries distributed from these
sources) for a guix pack. Thanks
On Sat, Jul 24, 2021 at 2:48 PM Ricardo Wurmus <rekado@elephly.net> wrote:
>
>
> Andy Tai <atai@atai.org> writes:
>
> > question the Guix documentation says a bundle created from guix
> > pack
> > can run on machines running the Linux kernel. Does this mean
> > such a
> > bundle can possibly run on Linux kernel with any C library, or
> > just
> > GNU/Linux?
>
> The pack includes the C library, so the host C library does not
> matter.
>
> --
> Ricardo
--
Andy Tai, atai@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat: andytai1010
Year 2021 民國110年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能
next prev parent reply other threads:[~2021-07-25 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 21:06 guix pack on Linux kernel Andy Tai
2021-07-24 21:24 ` Andy Tai
2021-07-24 21:48 ` Ricardo Wurmus
2021-07-25 23:16 ` Andy Tai [this message]
2021-08-17 12:55 ` zimoun
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=CAJsg1E-U9cW_Pdx-5t3r1ODxFJ3-nCu+tecDeY-hYVn2N+QjHA@mail.gmail.com \
--to=atai@atai.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).