[gentoo-dev] /etc/profile

[gentoo-dev] /etc/profile

[messdev]

Why exporting global variables' mechanism is so complicated? It is not very 
,,user friendly'' to edit /etc/env.d/00basic to change some global variables, 
whitch then go to /etc/profile.env and then to /etc/profile... It's not 
intuitively. Or maybe there is some simpler way to edit it?


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] /etc/profile

[Alexander Gretencord]

On Thursday 28 November 2002 01:50, messdev wrote:
> Why exporting global variables' mechanism is so complicated?

Is it?

> It is not very ,,user friendly'' to edit /etc/env.d/00basic to change some
> global variables

Well, where's the problem? Instead of editing one file called /etc/profile you 
edit another file called /etc/env.d/something. How the mechanism of getting 
it into your shells environment works doesn't have to bother you.

> It's not intuitively. Or maybe there is some simpler way to edit it?

Well as said, what's not simple in editing _one_ file? You've always edited 
_one_ file.

Just think about what is achieved by this mechanism. It's a simple and good 
solution to a problem. And normal users usually don't change global settings 
anyway, but use their own .profile which is not affected by portage's 
handling of global profile entries. As a sysadmin you will appreciate 
gentoo's handling as packages can add to the global settings without messing 
around with the actual file.


Alex

-- 
"They that can give up essential liberty to obtain a little temporary safety 
deserve neither liberty nor safety."
Benjamin Franklin


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] /etc/profile

[messdev]

Ok. But when you try to learn how to define global variables it is difficult 
to make an idea, that u should do it in /etc/env.d/*

When you look into /etc/profile you can see `source /etc/profile.env` - then, 
when you look into /etc/profile.env, everything points, that u should change 
definitions exacly in this file - i wanna say, that it is a good idea to put 
the comment into /etc/profile.env, that this file is genereting by using 
/etc/env.d/* files, and the definitions of variables there.

Or maybe i'm wrong... :)

Messer.

--
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Re: /etc/profile

[Paul]

messdev <messdev@messer.homelinux.org>, on Fri Nov 29, 2002 [12:07:56 AM] said:
> Ok. But when you try to learn how to define global variables it is difficult 
> to make an idea, that u should do it in /etc/env.d/*
> 
> When you look into /etc/profile you can see `source /etc/profile.env` - then, 
> when you look into /etc/profile.env, everything points, that u should change 
> definitions exacly in this file - i wanna say, that it is a good idea to put 
> the comment into /etc/profile.env, that this file is genereting by using 
> /etc/env.d/* files, and the definitions of variables there.
> 
> Or maybe i'm wrong... :)
> 
> Messer.
> 
> --

	Hi;

	I agree, /etc/profile.env should have the same message at
the top as /etc/ld.so.conf, as they are both autogenerated by
env-update. Go ahead and make a bug report on bugs.gentoo.org.
It should be a trivial adjustment.

Paul
set@pobox.com

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] /etc/profile

[Martin Schlemmer]

On Fri, 2002-11-29 at 01:07, messdev wrote:
> Ok. But when you try to learn how to define global variables it is difficult 
> to make an idea, that u should do it in /etc/env.d/*
> 
> When you look into /etc/profile you can see `source /etc/profile.env` - then, 
> when you look into /etc/profile.env, everything points, that u should change 
> definitions exacly in this file - i wanna say, that it is a good idea to put 
> the comment into /etc/profile.env, that this file is genereting by using 
> /etc/env.d/* files, and the definitions of variables there.
> 

Nobody are stopping you from just adding what you need to the
bottom of /etc/profile ...


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



--
gentoo-dev@gentoo.org mailing list