1 |
On Sunday 23 September 2007, John R. Graham wrote: |
2 |
> On Thursday 20 September 2007, Mike Frysinger wrote: |
3 |
> > no, this cannot live in baselayout (the package that creates /root/), |
4 |
> > because it cannot be run everytime a user upgrades the baselayout |
5 |
> > package. no, it cannot be tied to USE=build (used to make stage1) or |
6 |
> > USE=bootstrap (use to make stage2) as the only time the /etc/skel/ -> |
7 |
> > /root/ sync can sanely happen is in the final steps of creating a stage3 |
8 |
> > ... and there is nothing to differentiate the creation of a stage3 from a |
9 |
> > normal build, nor is there a sane way to make sure baselayout is the very |
10 |
> > last package in the stage3 build step |
11 |
> |
12 |
> Mike, for my own education (well, mostly), could you clarify why putting |
13 |
> the copy of the appropriate files from /etc/skel -> /root into the |
14 |
> ebuild that creates them but tying that special action to USE=build |
15 |
> isn't an acceptable solution? You've said that it would mean a special |
16 |
> case for each ebuild that puts things into /etc/skel, but I believe |
17 |
> we're talking about one or two ebuilds here, and, besides, isn't the |
18 |
> ebuild the appropriate place for that sort of expertise to reside, or at |
19 |
> least, not an inappropriate place? |
20 |
|
21 |
the /etc/skel -> /root sync needs to happen at the very end of stage3 as that |
22 |
is the only place where you can state "all packages relevant to a default |
23 |
install have been merged" |
24 |
|
25 |
USE=build is for building a stage1 and generally speaking, there is no reason |
26 |
why baselayout cant be merged before any other package ... pretty much any |
27 |
depend listed in the baselayout ebuild are there to force a specific minimal |
28 |
version of a package and over time get dropped |
29 |
-mike |