From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix environment guix doesn't provide guix dependencies?
Date: Fri, 30 Sep 2016 08:22:47 -0700 [thread overview]
Message-ID: <87shshcszc.fsf@gmail.com> (raw)
In-Reply-To: <87d1jloam0.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 30 Sep 2016 14:06:31 +0200")
[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> "Thompson, David" <dthompson2@worcester.edu> skribis:
>
>> On Wed, Sep 28, 2016 at 5:20 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>>> Hi Chris,
>>>
>>> Chris Marusich <cmmarusich@gmail.com> skribis:
>>>
>>>> John Darrington <john@darrington.wattle.id.au> writes:
>>>
>>> [...]
>>>
>>>>> I don't think so. Running ./bootstrap is not part of the normal process for *building*
>>>>> guix - only for bootstrapping. But you are right - it is common to want to do that.
>>>>> For this reason I often run:
>>>>>
>>>>> guix environment guix --ad-hoc automake autoconf texinfo help2man
>>>>>
>>>>>
>>>>> But perhaps you are right - the manual might want to mention this.
>>>>>
>>>>> J'
>>>>
>>>> That makes sense. I feel like it used to provide all the dependencies,
>>>> including autoconf etc., but that was months ago, and I might be
>>>> mis-remembering. It works fine when I add the needed bootstrap
>>>> dependencies with --ad-hoc.
>>>
>>> In fact there’s a small time window during which “guix environment guix”
>>> doesn’t provide autoconf et al.: it’s when the ‘guix’ variable in (gnu
>>> packages package-management) refers to a released tarball instead of a
>>> Git checkout, since a build from tarball doesn’t depend on autoconf et
>>> al.
>>>
>>> So if you run “guix environment guix” on a commit different from
>>> v0.11.0 + 1, you effectively get all the dependencies.
>>>
>>> I admit this is a bit confusing. Not sure how to document/improve that.
>>>
>>> Ideas?
>>
>> How about a public guix-devel package that always builds from the Git repo?
>
> Good idea. I guess it could essentially be an alias for the current
> ‘guix-devel’. Could you look into it and update the docs accordingly?
>
> Thanks! :-)
I'll give this a shot. I'll send a little patch this weekend.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2016-09-30 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 4:18 guix environment guix doesn't provide guix dependencies? Chris Marusich
2016-09-28 4:54 ` John Darrington
2016-09-28 5:10 ` Chris Marusich
2016-09-28 12:46 ` Eric Bavier
2016-09-28 19:06 ` myglc2
2016-09-30 6:52 ` Chris Marusich
2016-09-28 21:20 ` Ludovic Courtès
2016-09-30 0:46 ` Thompson, David
2016-09-30 6:40 ` Chris Marusich
2016-09-30 12:06 ` Ludovic Courtès
2016-09-30 15:22 ` Chris Marusich [this message]
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=87shshcszc.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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.