unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>, 40977@debbugs.gnu.org
Subject: bug#40977: --load-path does not honor ~
Date: Thu, 30 Apr 2020 21:21:03 +0200	[thread overview]
Message-ID: <87y2qcsst3.fsf@nckx> (raw)
In-Reply-To: <52117c4b-3090-1ccf-5669-ff4c47935e19@crazy-compilers.com>

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

Hartmut, Zimoun,

Hartmut Goebel 写道:
> After processing options, guix need to "expanduser()" (as it is 
> called
> in Python) on all arguments which are paths.

If any Python (or other) software does this, it's broken.  File a 
bug there.

This is the wrong thing to do and makes the GNU system an 
inconsistent mess.  …OK, *more* of an inconsistent, loveable, mess 
;-)

It also makes

  $ sudo guix system --load-path=~/path/tp/my/project …

and

  $ sudo guix system -L ~/path/to/my/project -A mypackage …

suddenly result in different file names.

Please don't do it.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2020-04-30 19:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  8:15 bug#40977: --load-path does not honor ~ Hartmut Goebel
2020-04-30 15:31 ` zimoun
2020-04-30 16:37   ` zimoun
2020-04-30 16:42   ` Hartmut Goebel
2020-04-30 16:50     ` zimoun
2020-04-30 17:34       ` Danny Milosavljevic
2020-04-30 17:53         ` Leo Famulari
2020-04-30 18:14           ` zimoun
2020-05-02 13:14         ` Ludovic Courtès
2020-05-02 13:55           ` zimoun
2020-05-02 22:14             ` Ludovic Courtès
2020-04-30 19:21     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-04-30 20:54       ` zimoun
2020-05-01  6:51         ` Bengt Richter
2020-05-01 15:24       ` zimoun

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=87y2qcsst3.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=40977@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --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).