From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 31841@debbugs.gnu.org, Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: bug#31841: ./pre-inst-env guix system no longer works without ~/.config/guix
Date: Sat, 16 Jun 2018 03:51:19 -0400 [thread overview]
Message-ID: <87d0wr5fuw.fsf@netris.org> (raw)
In-Reply-To: <87602kro0h.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 15 Jun 2018 18:51:58 +0200")
flags 31841 + notabug
close 31841
thanks
Hi Ludovic,
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> If there's a good reason to avoid implementing Ricardo's suggestion, I
>> don't mind keeping my modified 'guix' script above, but I confess that I
>> don't yet understand the cause of your reluctance.
>
> Well I’m not opposed to it, but my first reaction was that it adds
> complexity, it’s redundant with the ‘configure’ checks, and one can
> always find other ways to make things break.
>
> Now, I agree that it would be useful for the use case you mentioned
> (build in ‘guix environment’ and run outside of it), so if you come
> up with a patch, that works for me!
Fair enough.
>> Anyway, it seems that my practice of running 'guix' from a private git
>> checkout is becoming increasingly awkward to arrange. I would be
>> pleased if this mode of operation were better supported.
>
> I do that (like every Guix developer I suppose) every day, so I don’t
> think it’s going to stop working any time soon.
>
> In this case, the requirement of a new dependency made the issue
> apparent but fundamentally nothing has changed. In particular,
> ~/.config/guix is not required any more than it was before, contrary to
> what the subject says.
Indeed, good points. I considered retitling this bug to "./pre-inst-env
guix system fails outside of the development environment" or "now
requires guile-sqlite3", but the more I think about it, the more this
seems like a non-issue.
> OK to close this issue?
Done, thanks.
Mark
next prev parent reply other threads:[~2018-06-16 7:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 2:24 bug#31841: ./pre-inst-env guix system no longer works without ~/.config/guix Mark H Weaver
2018-06-15 6:56 ` Rutger Helling
2018-06-15 10:56 ` myglc2
2018-06-15 11:24 ` Ricardo Wurmus
2018-06-15 11:45 ` Ludovic Courtès
2018-06-15 12:04 ` Ricardo Wurmus
2018-06-15 13:08 ` Mark H Weaver
2018-06-15 13:40 ` Mark H Weaver
2018-06-15 16:51 ` Ludovic Courtès
2018-06-15 22:56 ` myglc2
2018-06-16 8:06 ` Mark H Weaver
2018-06-16 8:25 ` Ludovic Courtès
2018-06-16 9:50 ` Mark H Weaver
2018-06-16 14:31 ` George Clemmer
2018-06-17 20:53 ` Ludovic Courtès
2018-06-19 17:08 ` myglc2
2018-06-20 14:06 ` Ludovic Courtès
2018-06-16 7:51 ` Mark H Weaver [this message]
2018-06-17 12:54 ` bug#31841: Status: Guix requires guile-sqlite3 Maxim Cournoyer
2018-06-17 21:19 ` Ludovic Courtès
2018-06-18 1:34 ` Maxim Cournoyer
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=87d0wr5fuw.fsf@netris.org \
--to=mhw@netris.org \
--cc=31841@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).