System configuration, ~/.profile, custom path etc.

System configuration, ~/.profile, custom path etc.

[白い熊＠相撲道]

Hello:

I'm trying to understand the "desired" way to configure GuixSD, 
regarding modifying environment variables etc.

Studying the manual, it seems to me that the system doesn't source 
~/.profile etc. and instead the systematic way to modify the environment 
is via the sysconfig.scm file and system reconfigure.

Namely, I've found the "skeletons" variable, I've tried to undestand the 
example, but not sure I know how to implement it.

Let's say I want to add "~/sh" to PATH and also export TEST="This is a 
test."

How exactly do I add this to sysconfig.scm?

Many thanks.
-- 
白い熊＠相撲道

Re: System configuration, ~/.profile, custom path etc.

[Andreas Enge]

On Mon, Mar 16, 2015 at 07:20:27PM +0100, 白い熊＠相撲道 wrote:
> Let's say I want to add "~/sh" to PATH and also export TEST="This is a
> test."
> How exactly do I add this to sysconfig.scm?

What speaks against doing this as a user in .bashrc?

Andreas

Re: System configuration, ~/.profile, custom path etc.

[白い熊＠相撲道]

On 2015-03-16 19:48, Andreas Enge wrote:
> On Mon, Mar 16, 2015 at 07:20:27PM +0100, 白い熊＠相撲道 wrote:
>> Let's say I want to add "~/sh" to PATH and also export TEST="This is a
>> test."
>> How exactly do I add this to sysconfig.scm?
> 
> What speaks against doing this as a user in .bashrc?
> 
> Andreas

The .bashrc created after install is readonly by default. I understand I 
can chmod it and change it, but I thought the reason for this is exactly 
that it is the idea of Guix to modify it via the skeleton pairs in 
sysconfig and not edit it directly.

Is this not so?
-- 
白い熊＠相撲道

Re: System configuration, ~/.profile, custom path etc.

[Ludovic Courtès]

白い熊＠相撲道 <guix-devel_gnu.org@sumou.com> skribis:

> The .bashrc created after install is readonly by default. I understand
> I can chmod it and change it, but I thought the reason for this is
> exactly that it is the idea of Guix to modify it via the skeleton
> pairs in sysconfig and not edit it directly.
>
> Is this not so?

No, it’s just an accident due to ‘useradd’ preserving the skeleton’s
permission bits.  The user’s dot files can be modified as they see fit;
they are not managed at all by Guix.

But that these files are created read-only is really a bug.  useradd(8)
doesn’t seem to have an option to change the permission bits, so we may
have to iterate over all the dot files after the useradd invocation to
change their permissions.  Better ideas?

Thanks,
Ludo’.