Re: guix running advice: correct?

[Julien Lepiller]

Ah, the guix pull profile comming first is not absolute. It's simply that some 
users might have installed guix in their default profile, and if that profile 
comes before guix pull, that huix will be used. Any guix upgrade will then 
doongrade your profile.

This shouldn't be ppssible anymore, since guix should do the right thing now 
when setting the shell profile files, and it would warn if you attempted a 
dpongrade.

Le 5 février 2023 00:16:37 GMT+01:00, Kyle Andrews <kyle@posteo.net> a écrit :
>
>Julien Lepiller <julien@lepiller.eu> writes:
>
>> Hi Andy,
>>
>> I'm the author of this advice. I think it's still correct. It's mostly
>> sanity checks that you would run to ensure you can get packages from
>> this channel. Most of it is scattered around the manual, mostly in the
>> manual installation documentation.
>>
>> ~/.config/guix/current is where your new guix (the one you pulled with
>> the channel) is installed. If it's not first in $PATH, you're at risk
>> that some other guix will be used instead.
>>
>> hash is a command that removes an entry from the shell's cache. If
>> this is your first pull, the guix you used comes from another location
>> that is recorded by the shell, so you have to clear the cache to use
>> the newly pulled guix. If your guix already comes from the correct
>> location, it'll be useless but it won't hurt.
>>
>> HTH!
>>
>> Le 3 janvier 2023 06:31:25 GMT+01:00, Andy Tai <atai@atai.org> a écrit :
>>>Hi, from this page
>>>https://framagit.org/tyreunom/guix-android/-/blob/master/README.md
>>>
>>>Important checks
>>>Make sure your guix environment is set up properly. You need to have
>>>~/.config/guix/current as the first item in your $PATH or you're going
>>>to run into troubles. Additionally, after running guix pull, make sure you
>>>run hash guix in any open terminal to make sure bash's cache is cleared of
>>>the old guix binary location.
>>>
>>>I wonder if the above is correct, as I do not recall seeing anything in
>>>Guix doc mentioning such advice or something to that effect (unless I
>>>missed it)
>
>Interesting. I too had never heard about this PATH recommendation and it
>seems contrary to some advice I do remember given in the cookbook about
>working with multiple profiles. For me, activating an extra profile
>places it's /bin and /sbin directories at the beginning of my PATH. I can
>only find ~/.config/guix/current/bin burried quite deep near the end.
>
>Do you have any advice on how regular end users could follow your
>recommendation?
>
>My naive hope would be that end users wouldn't have to think about
>it. Ideally if its that dangerous then updating the path would happen
>automatically when sourcing the etc/profile file inside a profile
>directory.
>
>Should the Guix Profiles in Practice section of the cookbook be updated
>to reflect this?
>
>
>
>