From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <ericbavier@centurylink.net>
Cc: Eric Bavier <bavier@cray.com>, 33010@debbugs.gnu.org
Subject: [bug#33010] [PATCH 2/3] gnu: Add guix-minimal.
Date: Mon, 15 Oct 2018 21:28:31 +0200 [thread overview]
Message-ID: <87tvlnc8m8.fsf@gnu.org> (raw)
In-Reply-To: <20181015092143.0ce224d4@centurylink.net> (Eric Bavier's message of "Mon, 15 Oct 2018 09:21:43 -0500")
Eric Bavier <ericbavier@centurylink.net> skribis:
> On Sun, 14 Oct 2018 23:42:58 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> Hi,
>>
>> ericbavier@centurylink.net skribis:
>>
>> > From: Eric Bavier <bavier@cray.com>
>> >
>> > * gnu/packages/guile.scm (guile-2.0.13): New variable.
>> > * gnu/packages/package-management.scm (guix)[arguments]: Adjust 'wrap-program'
>> > phase to handle "missing" inputs.
>> > (guix-minimal): New variable.
>>
>> What’s the intended use case? Is it to check that Guix compiles against
>> an old Guile 2.0 and without optional dependencies?
>
> Right, to make sure that what we're advertising to the outside
> world as far as minimum dependencies will actually work.
I see.
>> I wonder whether we should add packages “just” for this, especially
>> given that 2.0 support is reaching end-of-life and that 2.0.13 is pretty
>> old.
>
> This package would be updated as needed to reflect changes in Guix
> dependencies.
OK. It does sound like an interesting CI job, but maybe not great as a
package users can install. Though of course we can mark it as hidden
and then it’s just an easy way to write that CI job. Thoughts?
Ludo’.
next prev parent reply other threads:[~2018-10-15 19:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 1:52 [bug#33009] [PATCH 0/3] Some guile@2.0 patches ericbavier
2018-10-11 1:52 ` [bug#33011] [PATCH 1/3] gnu: guile2.0-guix: Fix build ericbavier
2018-10-14 21:39 ` Ludovic Courtès
2018-10-16 22:35 ` bug#33011: " Eric Bavier
2018-10-11 1:52 ` [bug#33010] [PATCH 2/3] gnu: Add guix-minimal ericbavier
2018-10-14 21:42 ` Ludovic Courtès
2018-10-15 9:02 ` Efraim Flashner
2018-10-15 15:46 ` Jonathan Brielmaier
2018-10-15 19:26 ` Ludovic Courtès
2018-10-15 14:21 ` Eric Bavier
2018-10-15 19:28 ` Ludovic Courtès [this message]
2018-10-15 19:43 ` Eric Bavier
2018-10-16 11:28 ` Ludovic Courtès
2018-10-16 22:33 ` bug#33010: " Eric Bavier
2018-10-11 1:52 ` [bug#33012] [PATCH 3/3] ui: Fix port-buffering with guile@2.0 ericbavier
2018-10-14 21:43 ` Ludovic Courtès
2018-10-16 22:31 ` bug#33012: " Eric Bavier
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=87tvlnc8m8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33010@debbugs.gnu.org \
--cc=bavier@cray.com \
--cc=ericbavier@centurylink.net \
/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).