From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Michael Zucchi <notzed@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: practicality of custom config
Date: Wed, 01 Jan 2020 15:54:30 +0100 [thread overview]
Message-ID: <87d0c39qhl.fsf@ambrevar.xyz> (raw)
In-Reply-To: <955074b7-be07-ba7b-385a-1217e5c74afb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Michael Zucchi <notzed@gmail.com> 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 misunderstanding, I didn't mean to misquote you, I was
just giving an example in the style of Gentoo USE flags. The same holds
for "build without GUI support" for instance.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-01-01 14:54 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
2020-01-01 14:54 ` Pierre Neidhardt [this message]
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=87d0c39qhl.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=notzed@gmail.com \
/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).