Ricardo Wurmus writes:
Sergey Trofimov writes:
- adding it to guix increases maintenance burden: new versions
could
add or remove config options
This is why there should be automated tests. There are too few
of them.
that adds up to the pile of boilerplate to implement a simple
On 2023-12-27 05:41, Felix Lechner wrote:
Hi Luo Jing,
On Tue, Dec 26 2023, Jing Luo wrote:
Here is a reminder that I offered my computing resources
Unless folks here know you already, it might be helpful to tell the
list
more about what you do with that shiny and powerful equipment in
Hi,
I was adding to guix fail2ban, greetd services with their
configurations
and pending configuration for connman. Basically the overall idea
behind
guix (i.e. having declarative configuration) is really nice.
Having such
mechanism powered by general purpose language like scheme is
On 2023-12-26 at 17:50+01:00, Ricardo Wurmus wrote:
> Nguyễn Gia Phong writes:
> > On 2023-12-26 at 15:56+01:00, Ricardo Wurmus wrote:
> >> On 2023-12-26 at 14:53+01:00, Sergey Trofimov wrote:
> >> > - adding it to guix increases maintenance burden: new versions
> >> > could add or remove
Hi Luo Jing,
On Tue, Dec 26 2023, Jing Luo wrote:
> Here is a reminder that I offered my computing resources
Unless folks here know you already, it might be helpful to tell the list
more about what you do with that shiny and powerful equipment in your
living room. It would be an honor to get to
Nguyễn Gia Phong writes:
> [[PGP Signed Part:Undecided]]
> [1. text/plain]
> On 2023-12-26 at 15:56+01:00, Ricardo Wurmus wrote:
>> On 2023-12-26 at 14:53+01:00, Sergey Trofimov wrote:
>> > - adding it to guix increases maintenance burden: new versions
>> > could add or remove config options
Attila Lendvai writes:
> if you demand that e.g. all services accepted into guix have a
> configuration entry for every possible config field, and that the
> documentation of these fields are duplicated into the guix
> codebase... then whatever is included into guix will have a 100%
>
> > - adding it to guix increases maintenance burden: new versions could
> > add or remove config options
>
>
> This is why there should be automated tests. There are too few of them.
early detection of the breakage is just one part of the story. then it also
needs to be fixed -- before
On 2023-12-26 at 15:56+01:00, Ricardo Wurmus wrote:
> On 2023-12-26 at 14:53+01:00, Sergey Trofimov wrote:
> > - adding it to guix increases maintenance burden: new versions
> > could add or remove config options
>
> This is why there should be automated tests.
> There are too few of them.
This
Hi there,
I think specifying each option is too much to maintain - however I what about
an alist or hashmap?
Nixos has used the freeform module type to great success and this feels like
the same situation.
Sergey Trofimov writes:
> - adding it to guix increases maintenance burden: new versions could
> add or remove config options
This is why there should be automated tests. There are too few of them.
> - it requires documentation/translation, another hidden cost
We should only accept
Hi guix,
On 2023-12-26 14:44, Ada Stevenson wrote:
Hi,
On 12/22/23 8:11 PM, Andy Tai wrote:
Curious of the status of the future of Guix QA as package definition
contributors rely on it for updating packages (sending patches to get
accepted/committed) in guix...
I'm curious too. Did anything
Hi guix,
I want to start a discussion around how to manage user app config
files.
Copying my message from https://issues.guix.gnu.org/68010, where
home-zathura-configuration with 76 fields is proposed.
I have mixed feelings about pulling 3rd-party software
configurations in guix:
- adding
13 matches
Mail list logo
