[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: some questions about GUIX

From: Ludovic Courtès
Subject: Re: some questions about GUIX
Date: Wed, 30 Dec 2015 00:10:39 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Ricardo Wurmus <address@hidden> skribis:

> Sam Halliday <address@hidden> writes:
>> Ludovic Courtès <address@hidden> writes:


>>> Guix’s build daemon uses containers to perform isolated builds:
>> Interesting. I wonder if you wouldn't benefit from a docker / drone
>> network, just as a distribution mechanism for your own build farm. It
>> would be a shame to expend effort on that since it is somewhat something
>> of a solved problem (and purely a DevOps matter, not a user concern).
> Work is under way to distribute build artifacts over GNUnet.  Currently
> it is already possible to share build results over HTTP.  Ideally,
> package building is a distributed effort.  (We aren’t there yet.)

There’s also the offloading mechanism, which may be closer to what Sam
was mentioning:

>>>> * Issue tracker / comm channels
>>>> Will you be continuing to use debbugs, savannah and mailing lists going
>>>> forward or would you consider moving to a modern community management
>>>> system like gitlab?
>>> I hear the appeal of GitLab and the like.  However, as was recently
>>> discussed on guix-devel, while I think we must find ways to improve our
>>> workflows (for instance, tracking patches is becoming tricky), I don’t
>>> see us moving to one of those web-based approaches for several reasons:
>> I've never used GitLab, but I understand that it is free software. The
>> thread above seems to suggest that it is proprietary.
> There are two variants AFAIU; the hosted GitLab service uses the
> proprietary version.

Right, runs “GitLab EE”, which is proprietary.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]