1 |
Give me some decent time to go through the large amount of work you've |
2 |
done. You can't expect me to catch up in a few minutes, can you? Where |
3 |
possible, I'd like to commit stuff to the prefix portage sources, |
4 |
instead of patching separately. |
5 |
|
6 |
Thanks |
7 |
|
8 |
|
9 |
On 25-03-2009 10:43:51 +0100, Markus Duft wrote: |
10 |
> Hi! |
11 |
> |
12 |
> i'm done working on my prefix-chaining project for now. i have |
13 |
> (attached) patches ready for commit (and 2 new packages, but that should |
14 |
> not matter to anyone anyway :)) |
15 |
> |
16 |
> the one is a newer version of the portage patch i submitted lately, and |
17 |
> the other one patches baselayout, so that prefix chaining can work. |
18 |
> |
19 |
> for all these things i can say: they won't hurt anybody, as long as |
20 |
> there is no READONLY_EROOT set in make.conf, which should not be the |
21 |
> case ;) that's the trigger that activates all changes. |
22 |
> |
23 |
> if there is no READONLY_EROOT, behaviour of all parts of portage and |
24 |
> baselayout should be exactly the same. |
25 |
> |
26 |
> ok to commit? maybe we could think about checking the portage patch into |
27 |
> the prefix-portage svn tree? |
28 |
> |
29 |
> since i haven't commented on the baselayout patch yet, i'll do it here |
30 |
> (the portage patch is basically the same as the one i submitted lately, |
31 |
> with small improvements): |
32 |
> |
33 |
> etc/env.d/00basic: |
34 |
> * added EPREFIX variable, since if the currently used portage |
35 |
> instance comes from a chained prefix, portage needs to be |
36 |
> explicitly informed of the EPREFIX. this should not disturb |
37 |
> anybody, since it can be overridden after starting the prefix |
38 |
> again... |
39 |
> etc/profile: |
40 |
> * the profile now sources all profiles (recursively) of all |
41 |
> parent prefixes in the chain. |
42 |
> * if we are in a chained environment, some variables need |
43 |
> speacial treatment, since i want some of the chained envs to |
44 |
> be there in the current prefix. (PATH, MANPATH and in some |
45 |
> cases PKG_CONFIG_PATH. others may come...) |
46 |
> * if we are in a chained environment, don't append /usr/.. and |
47 |
> /... paths to PATH, unless we're the top level prefix in the |
48 |
> chain (which behaves the same as if there where no chain). |
49 |
> * the last hunk is for correctly setting the chained variables |
50 |
> which i listed above (PATH, MANPATH, etc.). |
51 |
> |
52 |
> Questions? |
53 |
> |
54 |
> If nobody has objections, i'll commit. i'll wait a few hours before |
55 |
> committing. |
56 |
> |
57 |
> Cheers, Markus |
58 |
|
59 |
|
60 |
|
61 |
|
62 |
-- |
63 |
Fabian Groffen |
64 |
Gentoo on a different level |