From: Ricardo Wurmus <rekado@elephly.net>
To: doron.behar@gmail.com
Cc: help-guix@gnu.org
Subject: Re: Trying to contribute packages: ./pre-inst-env doesn't work
Date: Wed, 15 May 2019 17:04:51 +0200 [thread overview]
Message-ID: <87a7fn7o8c.fsf@elephly.net> (raw)
In-Reply-To: <20190515144918.o524s4llrdvu7bcy@NUC.doronbehar.com>
Doron Behar <doron.behar@gmail.com> writes:
> On Wed, May 15, 2019 at 12:46:30PM +0200, Gábor Boskovits wrote:
>> > I ran the guix-daemon command:
>> >
>> > sudo -E ./pre-inst-env guix-daemon --build-users-group=guixbuild
>> >
>>
>> This should only be needed if you don't run it from a service manager.
>> Changes to the daemon are rare, and most of the times you should be
>> able to use the old daemon. But this should not cause a problem either.
>
> This what the docs say.
The Contributing section only says that you *can* run all of the tools
even before installation. It’s not wrong and in cases when you *don’t*
have a daemon running at all it is the right thing to do, but I agree
that in the more common case where you already *have* Guix it is
probably more confusing.
> There's so much room for improvements...
Do you have a constructive suggestion for improving this section of the
manual?
--
Ricardo
next prev parent reply other threads:[~2019-05-15 16:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 8:06 Trying to contribute packages: ./pre-inst-env doesn't work Doron Behar
2019-05-15 8:46 ` Gábor Boskovits
2019-05-15 9:46 ` Doron Behar
2019-05-15 10:22 ` Doron Behar
2019-05-15 10:46 ` Gábor Boskovits
2019-05-15 14:49 ` Doron Behar
2019-05-15 15:04 ` Ricardo Wurmus [this message]
2019-05-15 16:10 ` Doron Behar
2019-05-15 10:41 ` Gábor Boskovits
2019-05-15 14:31 ` Doron Behar
2019-05-15 16:33 ` Amirouche
2019-05-15 16:37 ` Amirouche
2019-05-15 21:26 ` Ricardo Wurmus
2019-05-16 9:30 ` Doron Behar
2019-05-15 9:08 ` pelzflorian (Florian Pelz)
2019-05-15 10:06 ` Doron Behar
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=87a7fn7o8c.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=doron.behar@gmail.com \
--cc=help-guix@gnu.org \
/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).