On Friday 21 September 2007, Chris Gianelloni wrote: > On Thu, 2007-09-20 at 20:52 -0400, Mike Frysinger wrote: > > On Thursday 20 September 2007, Chris Gianelloni wrote: > > > Also, my plan for this would be add the copying of the .bash* files > > > from /etc/skel if and only if USE=build *and* the files do not already > > > exist, done during pkg_preinst/pkg_postinst somewhere. This will pull > > > it into the stage1 tarball, making it available to everyone on all > > > further stages, it keeps it from being done every time someone emerges > > > bash, it doesn't stomp on existing files, and it doesn't show up in VDB > > > linked to the bash package. Is this acceptable? > > > > no, bash is not a special case > > > > why not add an `emerge --config baselayout` to the end of stage3 and i'll > > do the /root/ default setup in the baselayout ebuild > > I'd rather not do anything that isn't accomplished automatically by the > ebuild when it is being merged. If this really is so objectionable, I'd > just assume WONTFIX the request and move on with it.
as outlined already, it's objectionable in the sense that once a user has entered the system, nothing can be assumed in the automatic case. by the user running `emerge --config baselayout`, we can assume that the behavior it exhibits (for example, setting up files in /root that dont exist from /etc/skel/) is expected. as also explained, tying into USE=bootstrap and USE=build is not correct as that does not represent everything in stage3 and there is no way to detect the stage2->stage3 state vs a normal emerge. the compromise is simple: catalyst runs --config at the end of stage3 for appropriate packages, but as to what those things actually do is left in the ebuilds. -mike
signature.asc
Description: This is a digitally signed message part.
