Subject: [bug#60636] [PATCH] Add 'manifest.scm'

From: Maxim Cournoyer <[email-masked]>
Date: Wed, 11 Jan 2023 14:15:04 -0500

Hi,

Brian Cully <[email-masked]> 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