Maxim Cournoyer writes:
> Hi,
>
> 宋文武 writes:
>
>> Hello, commit 40310efde9b4a4f2cf98081d6cd10f843685ebb6 fix this by merge
>> search-paths from multiple profiles by `guix package --search-paths`, in
>> ~/.bashrc and ~/.zprofile (skeletons, so existed systems need manual
>> update).
>>
>>
>>
Josselin Poiret writes:
> Hi Maxim,
>
> Maxim Cournoyer writes:
>
>> Just to make sure, remove what exactly?
>
> Remove the bit in /etc/profile that loads the user's profile, if it is
> indeed supposed to be loaded by the user's own ~/.zprofile or
> ~/.bash_profile.
Remove will break existed
Hi Maxim,
Maxim Cournoyer writes:
> Just to make sure, remove what exactly?
Remove the bit in /etc/profile that loads the user's profile, if it is
indeed supposed to be loaded by the user's own ~/.zprofile or
~/.bash_profile. At least, I don't know if there is a general agreement
on what
Hi,
Josselin Poiret writes:
> Hi,
>
> 宋文武 via Bug reports for GNU Guix writes:
>
>> Hello, commit 40310efde9b4a4f2cf98081d6cd10f843685ebb6 fix this by merge
>> search-paths from multiple profiles by `guix package --search-paths`, in
>> ~/.bashrc and ~/.zprofile (skeletons, so existed systems
Hi,
宋文武 via Bug reports for GNU Guix writes:
> Hello, commit 40310efde9b4a4f2cf98081d6cd10f843685ebb6 fix this by merge
> search-paths from multiple profiles by `guix package --search-paths`, in
> ~/.bashrc and ~/.zprofile (skeletons, so existed systems need manual
> update).
>
>
> Close now!
Hi,
宋文武 writes:
> Hello, commit 40310efde9b4a4f2cf98081d6cd10f843685ebb6 fix this by merge
> search-paths from multiple profiles by `guix package --search-paths`, in
> ~/.bashrc and ~/.zprofile (skeletons, so existed systems need manual
> update).
>
>
> Close now!
Cool, thanks for the
Hello, commit 40310efde9b4a4f2cf98081d6cd10f843685ebb6 fix this by merge
search-paths from multiple profiles by `guix package --search-paths`, in
~/.bashrc and ~/.zprofile (skeletons, so existed systems need manual
update).
Close now!
Maxim Cournoyer (2021-06-28 00:48 -0400) wrote:
> Alex Kost writes:
[...]
>> I can modify /etc/profile with any "normal" linux distribution but I
>> cannot do it with the Guix System. And I find it awful that you think
>> it should stay like that. I am for providing as much freedom for a user
Am Montag, den 28.06.2021, 00:35 -0400 schrieb Maxim Cournoyer:
> Hi Leo,
>
> [...]
>
> > I think there is a solution, that works not only for the case of
> > disabling this unwanted feature, but also to add in support for
> > multiple profiles, i.e. if the user has more than just their .guix-
>
Hi Alex,
Alex Kost writes:
> Maxim Cournoyer (2021-06-25 22:37 -0400) wrote:
>
> [...]
>> Do you still have a vetted interest in the issue at hand? This is a
>> serious usability problem that's been in limbo for 6 years, apparently
>> for reasons of purity (not wanting to run a command in
Hi Leo,
[...]
> I think there is a solution, that works not only for the case of
> disabling this unwanted feature, but also to add in support for
> multiple profiles, i.e. if the user has more than just their .guix-
> profile to load.
>
> If we made this feature opt-in in that a user would
Maxim Cournoyer (2021-06-25 22:37 -0400) wrote:
[...]
> Do you still have a vetted interest in the issue at hand? This is a
> serious usability problem that's been in limbo for 6 years, apparently
> for reasons of purity (not wanting to run a command in /etc/profile).
> While I share the
Am Freitag, den 25.06.2021, 22:37 -0400 schrieb Maxim Cournoyer:
> Hello,
>
> Alex Kost writes:
>
> > zimoun (2020-02-21 16:53 +0100) wrote:
> >
> > > Dear,
> > >
> > > What is the status of the bug#20255 [1]?
> > > It is old; the last activity seems back on 2015, November. So let
> > >
Hello,
Alex Kost writes:
> zimoun (2020-02-21 16:53 +0100) wrote:
>
>> Dear,
>>
>> What is the status of the bug#20255 [1]?
>> It is old; the last activity seems back on 2015, November. So let resume.
>>
>> The issue is, e.g.:
>> - perl installed into the system profile
>> - perl-xml-parser
Ludovic Courtès (2015-11-24 20:22 +0300) wrote:
> Alex Kost skribis:
>
>> Ludovic Courtès (2015-11-21 23:10 +0300) wrote:
>
> [...]
>
>>> Really? Can you show the output of:
>>>
>>> time guix package -p /run/current-system/profile \
>>> -p
Alex Kost skribis:
> Ludovic Courtès (2015-11-24 20:22 +0300) wrote:
>
>> Alex Kost skribis:
>>
>>> Ludovic Courtès (2015-11-21 23:10 +0300) wrote:
>>
>> [...]
>>
Really? Can you show the output of:
time guix package -p
Alex Kost skribis:
> Ludovic Courtès (2015-11-21 23:10 +0300) wrote:
[...]
>> Really? Can you show the output of:
>>
>> time guix package -p /run/current-system/profile \
>> -p ~/.guix-profile --search-paths
>
> real 0m2.634s
> user 0m0.568s
> sys
Ludovic Courtès (2015-11-23 02:04 +0300) wrote:
> Alex Kost skribis:
>
>> Ludovic Courtès (2015-11-22 13:52 +0300) wrote:
>
> [...]
>
>> but it suits only the default case of a single user profile. If I
>> have several user profiles, it does nothing useful for me, only wastes
Alex Kost skribis:
> Ludovic Courtès (2015-11-22 13:52 +0300) wrote:
[...]
>> To me, what 宋文武 reported at the beginning of this thread is a
>> usability issue. We’ve hacked around it so far, but we know there are
>> cases where the hacks aren’t enough.
>>
>> We could
Alex Kost skribis:
>>> At first, because of the slowdown: it may be a few hundred milliseconds
>>> for you, but it's several seconds for me.
>>
>> Really? Can you show the output of:
>>
>> time guix package -p /run/current-system/profile \
>> -p
Ludovic Courtès (2015-11-22 13:52 +0300) wrote:
> Alex Kost skribis:
>
At first, because of the slowdown: it may be a few hundred milliseconds
for you, but it's several seconds for me.
>>>
>>> Really? Can you show the output of:
>>>
>>> time guix package -p
Ludovic Courtès (2015-11-21 11:57 +0300) wrote:
> Alex Kost skribis:
>
>> Ludovic Courtès (2015-11-20 01:32 +0300) wrote:
>>
>>> -# Load the system profile's settings.
>>> +if [ -x /run/current-system/profile/bin/guix ]
>>> +then
>>> + # Crucial variables such as 'MANPATH' or
Ludovic Courtès (2015-11-21 23:10 +0300) wrote:
> Alex Kost skribis:
>
>> Ludovic Courtès (2015-11-21 11:57 +0300) wrote:
>>
>>> Alex Kost skribis:
>>>
Ludovic Courtès (2015-11-20 01:32 +0300) wrote:
> -# Load the system profile's settings.
Alex Kost skribis:
> Ludovic Courtès (2015-11-21 11:57 +0300) wrote:
>
>> Alex Kost skribis:
>>
>>> Ludovic Courtès (2015-11-20 01:32 +0300) wrote:
>>>
-# Load the system profile's settings.
+if [ -x /run/current-system/profile/bin/guix ]
Alex Kost skribis:
> Ludovic Courtès (2015-11-20 01:32 +0300) wrote:
>
>> -# Load the system profile's settings.
>> +if [ -x /run/current-system/profile/bin/guix ]
>> +then
>> + # Crucial variables such as 'MANPATH' or 'INFOPATH' may be missing from
>> the
>> + # profiles'
Ludovic Courtès (2015-11-20 01:32 +0300) wrote:
> -# Load the system profile's settings.
> +if [ -x /run/current-system/profile/bin/guix ]
> +then
> + # Crucial variables such as 'MANPATH' or 'INFOPATH' may be missing from the
> + # profiles' individual 'etc/profile'. Thus, combine both
l...@gnu.org (Ludovic Courtès) skribis:
> 宋文武 skribis:
>
>>> [...]
The idea to generate profile from search-paths is not new,
I heard it from you IIRC.
I think it's the time to do it.
>>>
>>> Agreed, the plan makes sense and I think we have all the bits.
Some progress has been made: fc2d233 allows search paths for multiple
profiles to be combined.
So I think I will eventually (‘guix-devel’ needs to be updated first)
change /etc/profile to do:
eval `guix package -p /run/current-system/profile \
-p $HOME/.guix-profile --search-paths`
宋文武 iyzs...@gmail.com skribis:
How about using a shell variable as input for the location:
(replace /gnu/store/xxx with $GUIX_PROFILE)
# etc/profile
export PATH=$GUIX_PROFILE/bin:$PATH
export MANPATH=$GUIX_PROFILE/share/man:$MANPATH
...
Then when 'source' it, we pass the
宋文武 iyzs...@gmail.com skribis:
How about using a shell variable as input for the location:
(replace /gnu/store/xxx with $GUIX_PROFILE)
# etc/profile
export PATH=$GUIX_PROFILE/bin:$PATH
export MANPATH=$GUIX_PROFILE/share/man:$MANPATH
...
Then when 'source' it, we pass the
Ludovic Courtès l...@gnu.org writes:
宋文武 iyzs...@gmail.com skribis:
Or better to generate a 'profile' script for each manifest, and then
merged in shell level, so it can work out-of-the-box. How about:
- /etc/profile:
# configuration for the whole system goes here.
# shouldn't
宋文武 iyzs...@gmail.com skribis:
Or better to generate a 'profile' script for each manifest, and then
merged in shell level, so it can work out-of-the-box. How about:
- /etc/profile:
# configuration for the whole system goes here.
# shouldn't refer profile paths.
export
宋文武 iyzs...@gmail.com skribis:
[...]
The idea to generate profile from search-paths is not new,
I heard it from you IIRC.
I think it's the time to do it.
Agreed, the plan makes sense and I think we have all the bits.
A related question is whether to encode search path environment
宋文武 iyzs...@gmail.com writes:
[...]
The idea to generate profile from search-paths is not new,
I heard it from you IIRC.
I think it's the time to do it.
Agreed, the plan makes sense and I think we have all the bits.
A related question is whether to encode search path environment
[...]
The idea to generate profile from search-paths is not new,
I heard it from you IIRC.
I think it's the time to do it.
Agreed, the plan makes sense and I think we have all the bits.
A related question is whether to encode search path environment
variables into the manifest (currently
宋文武 iyzs...@gmail.com skribis:
As 'guix package' is for only one profile, that's fine.
Since we can get search-paths from system profile using:
guix package -p /run/current-system/profile --search-paths
Right.
I think the missing is to check whether we are under GuixSD,
and then merge
Currently, search-paths built only from packages in user's profile.
As reported by Andy Wingo in #guix, when I have:
perl installed into system profile
perl-xml-parser installed into user profile
guix package --search-paths won't give a hint about PERL5LIB,
so it's very likely end up with a
Ludovic Courtès l...@gnu.org writes:
宋文武 iyzs...@gmail.com skribis:
Currently, search-paths built only from packages in user's profile.
As reported by Andy Wingo in #guix, when I have:
perl installed into system profile
perl-xml-parser installed into user profile
guix package
宋文武 iyzs...@gmail.com skribis:
Currently, search-paths built only from packages in user's profile.
As reported by Andy Wingo in #guix, when I have:
perl installed into system profile
perl-xml-parser installed into user profile
guix package --search-paths won't give a hint about
39 matches
Mail list logo