unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Collin J. Doering" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 54631@debbugs.gnu.org
Subject: bug#54631: Unable to determine system origin when configuration stored in guix channel
Date: Wed, 30 Mar 2022 04:13:07 -0400	[thread overview]
Message-ID: <87bkxn3ktv.fsf@rekahsoft.ca> (raw)
In-Reply-To: <cc441b07385814f555d6894aaa0d2e06b360a6d9.camel@ist.tugraz.at>

Hi Liliana,

Thank you for your response :)

> Alternatively, Guix could take the expression specified via -e and
> write it to disk. 

I think this would be the best way to resolve this issue. Also, thanks for your explanation.

> LOAD_PATH tweaking should be considered harmful and void your
> provenance, at least w.r.t. channels.  There's no sane way for guix to
> check whether the load paths you added still exist after
> reconfiguration, other than placing the entire directory in the store.

I agree! However, I think it would be nice if `guix system describe`, `guix system list-generations`, `guix home list-generations`, etc.. indicated when a generation was created with the `-L|--load-path` argument specified. As you said, it 'voids you provenance', so I think its something that should be visually indicated to the user.

Regards

-- 
Collin J. Doering

http://rekahsoft.ca
http://blog.rekahsoft.ca
http://git.rekahsoft.ca




      reply	other threads:[~2022-03-30  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30  2:03 bug#54631: Unable to determine system origin when configuration stored in guix channel Collin J. Doering via Bug reports for GNU Guix
2022-03-30  5:56 ` Liliana Marie Prikler
2022-03-30  8:13   ` Collin J. Doering via Bug reports for GNU Guix [this message]

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=87bkxn3ktv.fsf@rekahsoft.ca \
    --to=bug-guix@gnu.org \
    --cc=54631@debbugs.gnu.org \
    --cc=collin@rekahsoft.ca \
    --cc=liliana.prikler@ist.tugraz.at \
    /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).