GNU bug report logs - #60636
[PATCH] Add 'manifest.scm'

Previous Next

Full log

Message #11 received at 60636 <at> debbugs.gnu.org (full text, mbox):

From: Brian Cully <bjc <at> spork.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 60636 <at> debbugs.gnu.org
Subject: Re: bug#60636: [PATCH] Add 'manifest.scm'
Date: Thu, 12 Jan 2023 09:18:18 -0500

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> This is intended for the Shepherd repository, right?

Yes. The shepherd documentation pointed me to the Guix ML and 
bugtracker. If there’s somewhere better, I can re-submit.

> The value this provides above 'guix shell -D shepherd' is that 
> it
> includes the build system bootstrapping packages too (autoconf,
> automake, etc.), right?

That’s correct. Shepherd can’t be built from a checkout using 
‘guix shell -D shepherd’ because (according to Ludo) Guix uses the 
tarball as a source, not the git repository. Ludo did mention on 
IRC that shepherd could probably use a manifest.scm when I asked 
him about it, but I don’t want to speak for him more than that.

> Are all these items really needed?  Why do we
> need GCC, or glibc or gettext for example?

I added every item in response to one of the build steps 
failing. GCC is needed, for instance, because configure tests for 
the existence of a working C compiler (probably because of 
etc/crash-handler.c, but I couldn’t say for sure), glibc is needed 
because we’ve got a C compiler in the mix, and gettext is needed 
for ‘autoconf-point’.

-bjc

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.