Re: practicality of custom config

Michael Zucchi writes: >> Indeed, in practice it's not easy to tell Guix "build a system without >> sound" or things like that. > > But I'm just using guix atop slackware64, and sound already works fine.  > There was no need to derisively misquote part of my query. Oh, sorry for the misundersta

Re: practicality of custom config

Hi, > From the manual: > >"It is also /customizable/: users can /derive/ specialized package >definitions from existing ones, including from the command line (see >Package Transformation Options > >

Re: practicality of custom config

On 31/12/19 8:20 pm, Pierre Neidhardt wrote: Hi Michael, Indeed, in practice it's not easy to tell Guix "build a system without sound" or things like that. But I'm just using guix atop slackware64, and sound already works fine.  There was no need to derisively misquote part of my query.

Re: practicality of custom config

Hi Michael, Indeed, in practice it's not easy to tell Guix "build a system without sound" or things like that. An option would be to implement a feature à-la USE flags (as in Portage on Gentoo). This was discussed previously here: https://lists.gnu.org/archive/html/guix-devel/2019-05/msg00285.ht

practicality of custom config

Morning, From the manual: "It is also /customizable/: users can /derive/ specialized package definitions from existing ones, including from the command line (see Package Transformation Options