unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.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: Fri, 15 Jun 2018 18:51:58 +0200	[thread overview]
Message-ID: <87602kro0h.fsf@gnu.org> (raw)
In-Reply-To: <87po0snp5g.fsf@netris.org> (Mark H. Weaver's message of "Fri, 15 Jun 2018 09:40:59 -0400")

Hello,

Mark H Weaver <mhw@netris.org> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:

[...]

>> I’m a bit reluctant to that, in part because it’s a development
>> environment where we can have different expectations IMO.
>
> 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!

> 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.

OK to close this issue?

Ludo’.

  reply	other threads:[~2018-06-15 16: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 [this message]
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
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=87602kro0h.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=31841@debbugs.gnu.org \
    --cc=mhw@netris.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).