From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Brian Cully <bjc@spork.org>
Cc: 60636@debbugs.gnu.org
Subject: [bug#60636] [PATCH] Add 'manifest.scm'
Date: Wed, 11 Jan 2023 14:15:04 -0500 [thread overview]
Message-ID: <87bkn4j32f.fsf@gmail.com> (raw)
In-Reply-To: <20230108002719.19791-1-bjc@spork.org> (Brian Cully's message of "Sat, 7 Jan 2023 19:27:19 -0500")
Hi,
Brian Cully <bjc@spork.org> writes:
> ---
> manifest.scm | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 manifest.scm
>
> diff --git a/manifest.scm b/manifest.scm
> new file mode 100644
> index 0000000..bdd4e64
> --- /dev/null
> +++ b/manifest.scm
> @@ -0,0 +1,29 @@
> +;; This is the complete list of Guix packages necessary for building Shepherd.
This is intended for the Shepherd repository, right?
> +;; For example the following shell command will run the built-in tests:
> +;;
> +;; % guix shell -m manifest.scm --pure -- make check
> +
> +(specifications->manifest
> + '("autoconf"
> + "automake"
> + "binutils"
> + "coreutils"
> + "diffutils"
> + "findutils"
> + "gawk"
> + "gcc"
> + "gettext"
> + "glibc"
> + "grep"
> + "guile"
> + "guile-fibers"
> + "guile-readline"
> + "help2man"
> + "libtool"
> + "make"
> + "pkg-config"
> + "sed"
> + "tar"
> + "texinfo"
> + "xz"))
The value this provides above 'guix shell -D shepherd' is that it
includes the build system bootstrapping packages too (autoconf,
automake, etc.), right? Are all these items really needed? Why do we
need GCC, or glibc or gettext for example?
Thanks for this contribution,
--
Maxim
next prev parent reply other threads:[~2023-01-11 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 0:27 [bug#60636] [PATCH] Add 'manifest.scm' Brian Cully via Guix-patches via
2023-01-11 19:15 ` Maxim Cournoyer [this message]
2023-01-12 14:18 ` Brian Cully via Guix-patches via
2023-01-12 22:31 ` Maxim Cournoyer
2023-01-13 2:01 ` [bug#60636] [PATCH v2] " Brian Cully via Guix-patches via
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=87bkn4j32f.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=60636@debbugs.gnu.org \
--cc=bjc@spork.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).