From: Michael Zucchi <notzed@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix <help-guix@gnu.org>
Subject: Re: practicality of custom config
Date: Wed, 1 Jan 2020 09:53:18 +1030 [thread overview]
Message-ID: <955074b7-be07-ba7b-385a-1217e5c74afb@gmail.com> (raw)
In-Reply-To: <87o8voddtf.fsf@ambrevar.xyz>
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.
> 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.html
>
> I'm planning to work on it in the coming weeks. Feedback welcome!
> Stay tuned!
>
Ok cheers, that's the sort of thing I was curious about. It seems involved.
Z
next prev parent reply other threads:[~2019-12-31 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 23:29 practicality of custom config Michael Zucchi
2019-12-31 9:50 ` Pierre Neidhardt
2019-12-31 23:23 ` Michael Zucchi [this message]
2020-01-01 14:54 ` Pierre Neidhardt
2020-01-01 9:34 ` Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=955074b7-be07-ba7b-385a-1217e5c74afb@gmail.com \
--to=notzed@gmail.com \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).