From: zimoun <zimon.toutoune@gmail.com>
To: Bengt Richter <bokr@bokr.com>
Cc: 43960@debbugs.gnu.org, "Дмитрий Поляков" <liltechdude@gmail.com>
Subject: bug#43960:
Date: Mon, 19 Oct 2020 19:01:24 +0200 [thread overview]
Message-ID: <87o8kyf8uz.fsf@gmail.com> (raw)
In-Reply-To: <20201015163923.GA4601@LionPure> (Bengt Richter's message of "Thu, 15 Oct 2020 18:39:23 +0200")
Dear,
On Thu, 15 Oct 2020 at 18:39, Bengt Richter <bokr@bokr.com> wrote:
>> On Thu, 15 Oct 2020 at 15:53, Bengt Richter <bokr@bokr.com> wrote:
>>
>> > If there is a left-over from old manual installation advice like
>> > --8<---------------cut here---------------start------------->8---
>> > /usr/local/bin/guix:
>> > symbolic link to /var/guix/profiles/per-user/root/current-guix/bin/guix
>> > --8<---------------cut here---------------end--------------->8---
>> > could it interfere in any way with the above, or subsequent operation?
I do not think it interferes.
> Yes. I didn't realize it was still there -- I may mis-remember some discussion
> deprecating the use of /usr/local/* to affect the namespace seen when typing
> guix whatever.
> (vs putting needed info in ~/.bash_profile or ~/.profile)
I am not sure to understand what you mean. I should have missed such
discussions. Do you have pointers?
> I.e., even though the target is /var/guix/... it is not by way of
> ~/.guix-profile unless
> that's been put first in the path via ~/.bash_profile.
>
> But /usr/local/bin is typically on a default PATH, so could you not
> accidentally see the
> wrong guix (rather than a more informative file-not-found) if the enviroment
> was not
> straight-forwardly inherited from a normal login? (e.g. emacs subshell pts?
> Haven't checked ;)
I am sorry, I do not understand your point. On Debian, fresh user:
--8<---------------cut here---------------start------------->8---
$ ls -a
. .. .bash_logout .bashrc .profile
$ which guix
/usr/local/bin/guix
$ guix pull
[..]
hint: Consider setting the necessary environment variables by running:
GUIX_PROFILE="/home/kikoo/.config/guix/current"
. "$GUIX_PROFILE/etc/profile"
Alternately, see `guix package --search-paths -p "/home/kikoo/.config/guix/current"'.
hint: Run `guix pull --news' to read all the news.
hint: After setting `PATH', run `hash guix' to make sure your shell refers to
`/home/kikoo/.config/guix/current/bin/guix'.
$ guix pull # again
nothing to be done
hint: Run `guix pull --news' to read all the news.
hint: After setting `PATH', run `hash guix' to make sure your shell refers to
`/home/kikoo/.config/guix/current/bin/guix'.
--8<---------------cut here---------------end--------------->8---
Is your point that:
guix install hello
will install ’hello’ from the Guix at version of ’/usr/local/bin/guix’?
Well, if you see improvements in this area, please open a separate
bug/whishlist report.
All the best,
simon
next prev parent reply other threads:[~2020-10-19 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 12:54 bug#43960: incompatible bytecode version Дмитрий Поляков
2020-10-12 15:29 ` zimoun
2020-10-12 16:07 ` bug#43960: Дмитрий Поляков
2020-10-12 17:53 ` bug#43960: Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-10-15 7:53 ` bug#43960: Ludovic Courtès
2020-10-15 9:47 ` bug#43960: zimoun
2020-10-15 13:52 ` bug#43960: Bengt Richter
2020-10-15 13:56 ` bug#43960: zimoun
2020-10-15 16:39 ` bug#43960: Bengt Richter
2020-10-19 17:01 ` zimoun [this message]
2020-10-25 22:33 ` bug#43960: Miguel Ángel Arruga Vivas
2020-10-26 15:06 ` bug#43960: zimoun
2021-11-21 6:18 ` bug#43960: incompatible bytecode version 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=87o8kyf8uz.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=43960@debbugs.gnu.org \
--cc=bokr@bokr.com \
--cc=liltechdude@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).