[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guix Days: Patch flow discussion
From: |
Clément Lassieur |
Subject: |
Re: Guix Days: Patch flow discussion |
Date: |
Tue, 06 Feb 2024 13:09:15 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
On Tue, Feb 06 2024, Tomas Volf wrote:
> On 2024-02-05 23:08:29 +0100, Wilko Meyer wrote:
>> Guix offers ways to use packages outside of Guix proper in a pretty feasible
>> and maintainable way (manifests, setting up channels), maybe promoting them
>> as
>> an alternative to having things in guix proper "as soon as possible" (as
>> that's not the only option to have things in a usable form) would be
>> beneficial.
>
> I would just like to point out that while this applies to packages, it is bit
> more complicated for services and other core parts of the Guix. Combined with
> the fact that Guix severely restricts what workflow model can forks use (e.g.
> merge not being possible if the fork should be authenticated), maintaining
> non-package modifications for longer periods of time can be a hassle.
Hi! Why is it more complicated with services? You don't need forks at
all to use packages and services outside of Guix proper.
Re: Guix Days: Patch flow discussion, Steve George, 2024/02/05
Re: Guix Days: Patch flow discussion, Clément Lassieur, 2024/02/05
Re: Guix Days: Patch flow discussion, Steve George, 2024/02/05
Re: Guix Days: Patch flow discussion, Hartmut Goebel, 2024/02/05