From: Leo Famulari <leo@famulari.name>
To: Adam <adam.quandour@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Packaging a repository with git submodules
Date: Sat, 9 Nov 2024 19:14:23 -0500 [thread overview]
Message-ID: <Zy_63xutOyjjB5s2@jasmine.lan> (raw)
In-Reply-To: <CA+jnL0MztN+vJVRQtPc-K4VK1rvaZMRU9dNc=BHshher33Rovg@mail.gmail.com>
On Thu, Nov 07, 2024 at 03:34:48PM +0300, Adam wrote:
> If I want to write a package for a git repository which has submodules,
> should I download these dependencies recursively (recursive? #t)? Or it
> will be better to write a package definition for each dependency?
Both approaches are good. It's a matter of taste and the particulars of
your package.
Some programs have a build system that makes it really hard to use
externally provided dependencies rather than the Git submodules. And
it's easier to use recursive Git as a packager.
On the other hand, if you use recursive Git, you lose the full power of
Guix to inspect and manipulate your package's dependency graph.
next prev parent reply other threads:[~2024-11-10 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 12:34 Packaging a repository with git submodules Adam
2024-11-10 0:14 ` Leo Famulari [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-09 20:37 Cayetano Santos
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=Zy_63xutOyjjB5s2@jasmine.lan \
--to=leo@famulari.name \
--cc=adam.quandour@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).