From: "dabbede@gmail.com" <dabbede@gmail.com>
To: help-guix@gnu.org
Subject: Creating a package using two sources/origins
Date: Mon, 12 Dec 2022 23:35:22 +0100 [thread overview]
Message-ID: <CAEwYQ4RBTdv=uRZiDSy6CqxAuK3Lx7ciA5nHHXQ0dWfuPjDQzg@mail.gmail.com> (raw)
Dear Guix members,
I would like to contribute to the project by creating a package for
linux-xenomai (a real-time extension to the linux kernel, see
https://source.denx.de/Xenomai/xenomai/-/wikis/home).
My issue is that, according to xenomai's build instructions, I am
supposed to use both a mainstream patched kernel (I'm pretty sure that
a deblobbed linux-libre kernel can work too) and a .tar.bz2 source
tree that contains the user-space libraries and binaries but also some
scripts for preparing the kernel before building.
By looking into linux-libre package definition, I see no problem in
downloading and patching the proper kernel source, however I don't
understand how I am supposed to specify in the package definition that
we need an additional source tree in the build process.
What would you suggest? Using snippets or additional build-phases?
Either way, I'm not skilled enough to download a compressed tar and
unpack it in a reachable directory at the build stage. I'm only aware
of the package's "origin" function to accomplish that. What is the
best way to do the same in a snippet or phase?
Thanks for the advice. I need this input to study more the topic ;-)
Regards, Davide
next reply other threads:[~2022-12-12 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 22:35 dabbede [this message]
2022-12-12 22:43 ` Creating a package using two sources/origins (
2022-12-12 23:58 ` dabbede
2022-12-13 6:17 ` (
2022-12-13 20:56 ` dabbede
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='CAEwYQ4RBTdv=uRZiDSy6CqxAuK3Lx7ciA5nHHXQ0dWfuPjDQzg@mail.gmail.com' \
--to=dabbede@gmail.com \
--cc=help-guix@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.
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).