From: Leo Famulari <leo@famulari.name>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Guile 2.0.13
Date: Sat, 15 Oct 2016 15:46:32 -0400 [thread overview]
Message-ID: <20161015194632.GB8809@jasmine> (raw)
In-Reply-To: <20161015171311.GB14171@macbook42.flashner.co.il>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
On Sat, Oct 15, 2016 at 08:13:12PM +0300, Efraim Flashner wrote:
> On Thu, Oct 13, 2016 at 11:11:38PM +0200, Ludovic Courtès wrote:
> >
> > More generally, we could try to have a “staging” branch for safe changes
> > that involve a rebuild of between ~300 and ~1200 packages, that we’d
> > merge more frequently than ‘core-updates’ (I think the Nix folks do
> > that). By “safe” I mean things like ungrafting, minor upgrades and
> > improvements; the goal would be to reduce the latency for such changes.
> >
> > Things that rebuild more than ~1200 packages would still go to
> > ‘core-updates’.
> >
> > WDYT?
> >
> > Thanks!
> >
> > Ludo’.
> >
>
> This sounds like a good idea in general. A quick `guix refresh -l cmake'
> showed ~1100 packages, which would make this a good spot for the patch I
> tossed into core-updates to also build the ccmake binary.
+1
> Currently I think most of us try to keep the number of rebuilds under
> ~150, so it might be nice to have some sort of guidelines in a separate
> post (and in HACKING eventually) so that people don't miss it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-10-15 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 12:38 Guile 2.0.13 Ludovic Courtès
2016-10-12 16:20 ` Christopher Allan Webber
2016-10-12 16:35 ` Leo Famulari
2016-10-12 18:26 ` Christopher Allan Webber
2016-10-12 20:13 ` Ludovic Courtès
2016-10-12 20:30 ` Leo Famulari
2016-10-13 21:11 ` Ludovic Courtès
2016-10-15 17:13 ` Efraim Flashner
2016-10-15 19:46 ` Leo Famulari [this message]
2016-10-18 14:26 ` 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=20161015194632.GB8809@jasmine \
--to=leo@famulari.name \
--cc=efraim@flashner.co.il \
--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.