From: Ian Eure <ian@retrospec.tv>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: guix-devel@gnu.org
Subject: Re: Proposal: nss updates
Date: Thu, 27 Jun 2024 13:56:25 -0700 [thread overview]
Message-ID: <877cea3xtf.fsf@meson> (raw)
In-Reply-To: <87v81uwe48.fsf@lease-up.com>
Hi Felix,
Felix Lechner <felix.lechner@lease-up.com> writes:
> Hi Ian,
>
> On Thu, Jun 27 2024, Ian Eure wrote:
>
>> The nss package updates frequently, around once a month. [...]
>> I'm
>> considering options to balance update frequency vs. huge
>> rebuilds.
>
> Your plan sounds reasonable but my opinion is inconsequential.
> Instead,
> I'd like to point out that you are not alone:
>
> Wouldn't you like it if two days a month were set aside to allow
> uploads
> that trigger large rebuilds? The approach would pool intensive
> uploads
> in the time domain rather than how we do it now in space, namely
> branches.
>
I think this is probably a good idea, though the implementation
might be difficult to manage. I’m not sure where the patches
would go if not some short-lived branch, so we’d still likely have
the space complexity. A one-month timebox for large changes,
where they merge or get backed out at the end, seems like it could
be a reasonable way to break down some of the long-running
branches.
One thing we should be considerate of is users with limited
bandwidth. Even if Guix has the compute to build and bandwidth to
serve, not all of its users will.
Thanks,
— Ian
next prev parent reply other threads:[~2024-06-27 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 14:13 Proposal: nss updates Ian Eure
2024-06-27 16:21 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-27 20:56 ` Ian Eure [this message]
2024-07-01 2:50 ` Maxim Cournoyer
2024-07-01 15:00 ` Ian Eure
2024-07-01 20:31 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-07-02 0:06 ` Ian Eure
2024-07-02 1:57 ` Maxim Cournoyer
2024-08-15 23:38 ` Ian Eure
2024-08-18 14:10 ` Maxim Cournoyer
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=877cea3xtf.fsf@meson \
--to=ian@retrospec.tv \
--cc=felix.lechner@lease-up.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.