On Sunday 23 September 2007, John R. Graham wrote: > On Thursday 20 September 2007, Mike Frysinger wrote: > > 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, for my own education (well, mostly), could you clarify why putting > the copy of the appropriate files from /etc/skel -> /root into the > ebuild that creates them but tying that special action to USE=build > isn't an acceptable solution? You've said that it would mean a special > case for each ebuild that puts things into /etc/skel, but I believe > we're talking about one or two ebuilds here, and, besides, isn't the > ebuild the appropriate place for that sort of expertise to reside, or at > least, not an inappropriate place?
the /etc/skel -> /root sync needs to happen at the very end of stage3 as that is the only place where you can state "all packages relevant to a default install have been merged" USE=build is for building a stage1 and generally speaking, there is no reason why baselayout cant be merged before any other package ... pretty much any depend listed in the baselayout ebuild are there to force a specific minimal version of a package and over time get dropped -mike
signature.asc
Description: This is a digitally signed message part.
