From: Alexandre Oliva <lxoliva@fsfla.org>
To: Leo Famulari <leo@famulari.name>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: linux-libre source tarballs
Date: Mon, 03 May 2021 13:39:54 -0300 [thread overview]
Message-ID: <orim3zixet.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <YI4SQtQSIQNvyApa@jasmine.lan> (Leo Famulari's message of "Sat, 1 May 2021 22:45:22 -0400")
Hello, Leo,
On May 1, 2021, Leo Famulari <leo@famulari.name> wrote:
> it's not "source code" in the GNU sense, which is the "preferred form
> of the work for making changes in it":
That's not accurate. Linux-libre sources, whether obtained from a git
repository or from a tarball, are just as suitable for kernel
development as any other snapshot.
There is an alternate understanding of source code form taking shape in
some communities that suggests that a version control repository is
somehow more "source"ish than any of the versions held in it.
No doubt the additional versions in it may be useful in some cases, but
it does not follow that other versions and their relationship are part
of "source code" in the GNU sense.
In the GNU sense, any individual snapshot or release meets the
definition of source code.
> Not to mention that cloning a 1 GB Git repo is rather expensive compared
> to downloading a tarball
You don't have to clone anything. If all you want is a tarball, use
'git archive --remote'.
> As you say, these tarballs are not available for very long.
*nod*, that's why we switched to a git repo, and extract the tarballs
from it.
Back when we made the switch, I wrote extensive documentation and
recipes as to the possibilities of getting to the GNU Linux-libre
sources from it, how to verify signatures, etc. It was to be assessed
by then maintainers of Guix recipes to build GNU Linux-libre before
publishing, but it doesn't look like I ever got feedback on them, and
they hvae been unpublished so far.
Is it correct to assume that they have never reached you? Would you
like to have a look and let me know whether they make sense to you? I'd
be glad to dig them up and share them with you, if so, and to take your
feedback towards making them available to the public at large.
Thanks,
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2021-05-03 16:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 1:45 linux-libre source tarballs Vagrant Cascadian
2021-05-02 2:45 ` Leo Famulari
2021-05-02 4:42 ` Leo Famulari
2021-05-02 21:08 ` Ludovic Courtès
2021-05-02 22:26 ` Leo Famulari
2021-05-02 22:38 ` Leo Famulari
2021-05-03 15:44 ` linux-libre source tarballs (disable "deblob-check"?) Leo Famulari
2021-05-03 16:39 ` Alexandre Oliva [this message]
2021-05-03 17:13 ` linux-libre source tarballs Leo Famulari
2021-05-06 4:10 ` Alexandre Oliva
2021-05-06 21:23 ` Leo Famulari
2021-05-06 20:30 ` Maxim Cournoyer
2021-05-09 3:27 ` Alexandre Oliva
2021-05-30 4:50 ` Vagrant Cascadian
2021-05-31 3:42 ` Leo Famulari
2021-05-31 19:57 ` Mathieu Othacehe
2021-08-01 20:45 ` source tarballs potentially built for each derivation Vagrant Cascadian
2021-08-01 21:04 ` Vagrant Cascadian
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=orim3zixet.fsf@lxoliva.fsfla.org \
--to=lxoliva@fsfla.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=vagrant@debian.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.