From: ludo@gnu.org (Ludovic Courtès)
To: Dave Thompson <davet@fsf.org>
Cc: guix-devel@gnu.org, Dave Thompson <davet@gnu.org>
Subject: Re: [PATCH 0/2] Improve search path handling?
Date: Mon, 02 Mar 2015 15:27:42 +0100 [thread overview]
Message-ID: <87egp75va9.fsf@gnu.org> (raw)
In-Reply-To: <8dr3t7sf7v.fsf@freestation00.office.fsf.org> (Dave Thompson's message of "Mon, 02 Mar 2015 08:26:12 -0500")
Dave Thompson <davet@fsf.org> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> Andreas Enge <andreas@enge.fr> writes:
>>>
>>>> On Sat, Feb 28, 2015 at 12:31:59PM -0500, David Thompson wrote:
>>>>> Yes, I think so. I think I have resolved this, but it's a "rebuild the
>>>>> world" change so I don't yet know if it works. Would it be possible to
>>>>> add a 'wip-search-paths' branch for Hydra to build?
>>>>
>>>> Definitely! If you create and push such a branch, we can make it build on
>>>> hydra. But maybe now is the moment to push lots of stuff to core-updates
>>>> anyway (except that there have been so many changes recently, that I worry
>>>> if anything breaks, it will be difficult to determine why).
>>>
>>> I think we should just push this to 'core-updates' ASAP.
>>
>> I was about to enable whole-system builds for ‘core-updates’.
>>
>> David, do you want to try anyway or can you wait for the next round
>> (which I’ll expect will be soon, because there’s another bunch of core
>> changes I’d like to make)?
>
> I think we should wait for the next round. The patch that causes a
> rebuild hasn't been posted here yet, and when I tried to rebuild
> everything on my laptop something failed.
>
> Do you think it would be worth it to push these 2 patches now and do the
> refactoring/rebuild stuff later? If so, I think these can just go to
> master, because the build system isn't touched.
I’ve just set up Hydra to build core-updates, so let’s indeed wait for
the next round, it’s safer.
Thanks,
Ludo’.
prev parent reply other threads:[~2015-03-02 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 2:11 [PATCH 0/2] Improve search path handling? David Thompson
2015-02-24 2:19 ` [PATCH 1/2] packages: Merge like search path specifications David Thompson
2015-02-27 16:03 ` Ludovic Courtès
2015-02-24 2:19 ` [PATCH 2/2] packages: Add %base-search-path-specifications David Thompson
2015-02-27 16:04 ` Ludovic Courtès
2015-02-25 3:04 ` [PATCH 0/2] Improve search path handling? David Thompson
2015-02-27 16:06 ` Ludovic Courtès
2015-02-28 17:31 ` David Thompson
2015-02-28 20:36 ` Andreas Enge
2015-03-02 6:17 ` Mark H Weaver
2015-03-02 9:27 ` Ludovic Courtès
2015-03-02 13:26 ` Dave Thompson
2015-03-02 14:27 ` Ludovic Courtès [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=87egp75va9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=davet@fsf.org \
--cc=davet@gnu.org \
--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.