From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: jgart <jgart@dismail.de>
Cc: Morgan Smith <Morgan.J.Smith@outlook.com>,
52897-done@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#52897] [PATCH] doc: Add instructions on upgrading the build daemon with doas.
Date: Fri, 08 Jul 2022 21:36:33 -0400 [thread overview]
Message-ID: <87ilo7m5i6.fsf@gmail.com> (raw)
In-Reply-To: <20220707191521.GN1675@gac> (jgart@dismail.de's message of "Thu, 7 Jul 2022 19:15:21 -0500")
Hi jgart,
jgart <jgart@dismail.de> writes:
> On Thu, 07 Jul 2022 14:27:47 -0400 Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>> Hello,
>>
>> zimoun <zimon.toutoune@gmail.com> writes:
>>
>> > Hi,
>> >
>> > On Fri, 31 Dec 2021 at 23:49, Morgan Smith <Morgan.J.Smith@outlook.com> wrote:
>> >
>> >> I've explicitly removed sudo from my machine as supposedly sudo is a
>> >> large complex codebase that likely has bugs (although that's probably
>> >> just openBSD propaganda).
>> >
>> > Guix documentation uniquely relies on ’sudo’. And for instance, I was
>> > not aware of such propaganda. :-)
>> >
>> > Well, I do not have an opinion, but AFAIK, Guix does not work on the top
>> > of OpenBSD (yet! who knows if someone will not port a BSD kernel with a
>> > GNU userland as Debian did some time ago [1] ;-))
>> >
>> > For me, it is a niche and for consistency, all the commands using ’sudo’
>> > should also provide the ’doas’ way. And I am not convinced the burden
>> > is worth. Well, I do not have an opinion.
>>
>> I'm also not convinced it brings much, especially since Guix can't be
>> used where 'doas' is likely to be encountered (BSDs).
>
> FWIW, I use doas on Debian and alpine linux was considering replacing sudo with doas ;()
>
> But, yes. This is low priority for me right now so that's fine to close it :)
>
> I may experiment with doas in a guix channel instead.
Note that me closing this issue was not against having 'doas' in Guix
(you are welcome to contribute a package for it if you like), it was
against offering 'doas' equivalents to 'sudo' in our documentation.
Thanks,
Maxim
next prev parent reply other threads:[~2022-07-09 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 11:11 [bug#52897] [PATCH] doc: Add instructions on upgrading the build daemon with doas jgart via Guix-patches via
2021-12-30 14:55 ` zimoun
2022-01-01 4:49 ` Morgan Smith
2022-01-03 17:01 ` zimoun
2022-07-07 18:27 ` bug#52897: " Maxim Cournoyer
2022-07-08 0:15 ` [bug#52897] " jgart via Guix-patches via
2022-07-09 1:36 ` Maxim Cournoyer [this message]
2022-07-09 4:53 ` jgart via Guix-patches via
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=87ilo7m5i6.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=52897-done@debbugs.gnu.org \
--cc=Morgan.J.Smith@outlook.com \
--cc=jgart@dismail.de \
--cc=zimon.toutoune@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).