From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Make "guix-devel" a public variable in package-management.scm
Date: Tue, 18 Oct 2016 16:24:14 +0200 [thread overview]
Message-ID: <87funtivld.fsf@gnu.org> (raw)
In-Reply-To: <8737k617my.fsf@gmail.com> (Chris Marusich's message of "Sat, 08 Oct 2016 21:14:13 -0700")
Hi Chris,
Chris Marusich <cmmarusich@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
[...]
>> (define-public guix guix-devel)
>>
>> +(define-public guix-for-environment
>> + ;; We provide this pseudo-package just to allow people to run:
>> + ;; guix environment guix-devel
>> + ;; to reliably get the development environment for Guix (using 'guix' for
>> + ;; this purpose does not work when 'guix' points to the built-from-tarball
>> + ;; package rather than to the built-from-checkout package.)
>> + (package
>> + (inherit guix-devel)
>> + (name "guix-devel")
>> + (source #f) ;not meant to be built
>> + (supported-systems '())))
>> +
>> (define (source-file? file stat)
>> "Return true if FILE is likely a source file, false if it is a typical
>> generated file."
>>
>>
>> ?
>>
>> If that’s fine with you, could you incorporate it in your patch?
>
> Sounds good to me. I've attached the updated patch to this email and
> mentioned you as co-author. The new package fails to build with a
> cryptic error, but since it isn't meant to be built, that seems OK.
>
> What is the purpose of temporarily changing the "guix" variable to refer
> to the release package (as in commit 4420940f)? Because it usually
> refers to the development version, wouldn't it be better to make the
> "guix" variable ALWAYS refer to the development version? It isn't clear
> to me why we need to temporarily change this variable to refer to the
> release version.
Somehow this question turned out to be difficult to answer to me, which
contributed to the delay. ;-)
I think you’re right: in a way, this is a bit silly. This is a purist’s
approach (when we have the tarball, no need to depend on Autoconf et
al.), but it would work just fine if we simply added the ‘native-inputs’
currently on ‘guix-devel’ to ‘guix-0.11.0’ itself.
If there are no objections, I’ll just do that.
Thanks, and sorry for taking so long for such a simple answer!
Ludo’.
next prev parent reply other threads:[~2016-10-18 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 21:42 [PATCH] gnu: Make "guix-devel" a public variable in package-management.scm Chris Marusich
2016-10-05 21:35 ` Ludovic Courtès
2016-10-09 4:14 ` Chris Marusich
2016-10-18 14:24 ` Ludovic Courtès [this message]
2016-10-30 22:21 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87funtivld.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.