all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 43960@debbugs.gnu.org, "Дмитрий Поляков" <liltechdude@gmail.com>
Subject: bug#43960:
Date: Thu, 15 Oct 2020 18:39:23 +0200	[thread overview]
Message-ID: <20201015163923.GA4601@LionPure> (raw)
In-Reply-To: <CAJ3okZ2chcK-J9Bn0+Mxjtyd4U9e6439kL9hYLPo8Mn4JY9ztw@mail.gmail.com>

Hi Simon,

On +2020-10-15 15:56:41 +0200, zimoun wrote:
> Hi Bengt,
> 
> 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?
> 
> You mean the step #6 from the manual [1], right?
>

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

Also doesn't the ".../per-user/root/..." part in the link make you dependent
on the result of _sudo_ guix pull, not plain guix pull? (or are they equivalent somehow?)

IDK, but I really don't like typing "sudo guix ..." any better than "sudo firefox" or "sudo python"
or "sudo <anything I can't completely predict what files condition the outputs or where they go>"

I hope we can get to 100%-user-mode guix. Maybe offloading to containerized guix
systems could be a model for swarms of cooperating user-mode peers (modulo some protocol
for synchronizing versions identified by guix describe) for distributed challenges,
and normal usage would run guix with a localhost swarm providing the guix user-mode-daemons ;)

> 1: <https://guix.gnu.org/devel/manual/en/guix.html#Binary-Installation>
> 
> 
> All the best,
> simon

Sorry if this is only illustrating my noob misconceptions :)

-- 
Regards,
Bengt Richter




  reply	other threads:[~2020-10-15 16:40 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             ` Bengt Richter [this message]
2020-10-19 17:01               ` bug#43960: zimoun
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201015163923.GA4601@LionPure \
    --to=bokr@bokr.com \
    --cc=43960@debbugs.gnu.org \
    --cc=liltechdude@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.