Re: [gentoo-dev] Why isn't /root/.bash_profile in the stage tarballs?

[Mike Frysinger]

On Thursday 20 September 2007, Chris Gianelloni wrote:
> On Thu, 2007-09-20 at 03:03 -0400, Mike Frysinger wrote:
> > what catalyst should do is just before cleaning up the stage3 root and
> > packing it up is run `rsync -a /etc/skel/ /root/`
>
> It definitely should not.  One of my primary motivations with catalyst
> is to ensure that the users get *exactly* what would be provided by the
> profiles/packages.  We don't add extra files into the stages and likely
> never will.  Doing something like this in catalyst would create an
> inconsistency between doing a stage3 install and any previous stage
> installs.  Yes, we don't support stage1 anymore, but we still support
> stage1 users once their systems are up and running.  Having them
> inconsistent only causes one more area where we have to do extra
> troubleshooting to determine the cause.

not really ... someone installing by hand and someone taking a default setup 
are different things.  we know that someone taking a stage3 has never 
configured anything before and so we can safely put defaults into /root/.  we 
have no idea what people have done when they run emerge themselves.  that is 
why only putting this into catalyst makes sense.

> > 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
>
> Well, it depends on whether we're interested in getting all of /etc/skel
> or just the .bash* files.  About the only thing I would see useful as
> "defaults" is the .bash* stuff and a .ssh directory.  I do agree that
> everything else should be left up to the user.  If we decided what to
> include and limited it, it shouldn't be a problem to do it via USE=build
> at all.

anything that is part of the system /etc/skel/ makes sense (iow, anything that 
is in /etc/skel/ at the end of stage3).  the files from bash and the .ssh dir 
are the only things that go into /etc/skel/ right now for the default system.
-mike