On Wednesday 19 September 2007, Andrew Gaffney wrote:
> John R. Graham wrote:
> > On the forums, I've seen the question, "Why isn't my .bashrc being
> > executed when I log in as root but is being executed when I log in as a
> > normal user?," asked half a dozen times on the forums. Heck, I even
> > asked it myself a few years ago. Now, two years later, from a slightly
> > more mature level of domain knowledge, I have to ask why the root cause
> > shouldn't be addressed. Why can't the simple little default
> > .bash_profile from /etc/skel be put into /root as well?
>
> When catalyst builds a stage tarball, it doesn't add any additional files.
> All files in any stage tarball are created by one of the packages contained
> within. In order to do this, a package such as baselayout would have to
> install the file.
>
> Looking at my local install, it's actually bash that creates
> /etc/skel/.bash{rc,_logout,_profile}. You can appeal to the maintainer(s)
> of the bash ebuild (should be the base-system herd) to add that
> functionality, but I really doubt you'll convince them.the issue is hardly limited to bash ... by this argument, you propose to have every package which could possibly install into /etc/skel/ have special case code to also install into /root/ what catalyst should do is just before cleaning up the stage3 root and packing it up is run `rsync -a /etc/skel/ /root/` no, this cannot live in baselayout (the package that creates /root/), because it cannot be run everytime a user upgrades the baselayout package. no, it cannot be tied to USE=build (used to make stage1) or USE=bootstrap (use to make stage2) as the only time the /etc/skel/ -> /root/ sync can sanely happen is in the final steps of creating a stage3 ... and there is nothing to differentiate the creation of a stage3 from a normal build, nor is there a sane way to make sure baselayout is the very last package in the stage3 build step -mike
signature.asc
Description: This is a digitally signed message part.
