From: jlicht@fsfe.org
To: 61454@debbugs.gnu.org
Cc: Jelle Licht <jlicht@fsfe.org>
Subject: [bug#61454] [PATCH 0/5] Expose upstream linux sources
Date: Sun, 12 Feb 2023 16:39:55 +0100 [thread overview]
Message-ID: <cover.1676213809.git.jlicht@fsfe.org> (raw)
From: Jelle Licht <jlicht@fsfe.org>
Hey guix,
This patch series should not lead to any rebuilds. The aim is to expose the
used linux upstream sources, for use by custom local packages or external
channels.
Two main concerns I still have:
* Is this fundamentally going to be an issue with the FSDG?
* This is the 'dumb' solution; alternatively, I was thinking of introducing a
record to unify all the moving parts (the upstream sources, the deblob
scripts) involved in building our linux-libre kernels. That bigger change is
ideally something we achieve consensus on before writing some code.
Jelle Licht (5):
gnu: linux-libre 4.14: Expose upstream sources.
gnu: linux-libre 4.19: Expose upstream sources.
gnu: linux-libre 5.10: Expose upstream sources.
gnu: linux-libre 5.15: Expose upstream sources.
gnu: linux-libre 6.1: Expose upstream sources.
gnu/packages/linux.scm | 47 ++++++++++++++++++++++++------------------
1 file changed, 27 insertions(+), 20 deletions(-)
base-commit: fb9799ff5f1d90a443dc197535c48041ad6b3865
--
2.39.1
next reply other threads:[~2023-02-12 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 15:39 jlicht [this message]
2023-02-12 15:42 ` [bug#61454] [PATCH 1/5] gnu: linux-libre 4.14: Expose upstream sources jlicht
2023-02-12 15:42 ` [bug#61454] [PATCH 2/5] gnu: linux-libre 4.19: " jlicht
2023-02-12 15:42 ` [bug#61454] [PATCH 3/5] gnu: linux-libre 5.10: " jlicht
2023-02-12 15:42 ` [bug#61454] [PATCH 4/5] gnu: linux-libre 5.15: " jlicht
2023-02-12 15:42 ` [bug#61454] [PATCH 5/5] gnu: linux-libre 6.1: " jlicht
2023-02-12 16:46 ` [bug#61454] [PATCH 0/5] Expose upstream linux sources Liliana Marie Prikler
2023-02-12 18:53 ` Tobias Geerinckx-Rice via Guix-patches via
2023-02-12 19:23 ` bug#61454: " Jelle Licht
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=cover.1676213809.git.jlicht@fsfe.org \
--to=jlicht@fsfe.org \
--cc=61454@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).