1 |
On Wed, 2004-12-29 at 10:03 -0500, Chris Gianelloni wrote: |
2 |
> On Wed, 2004-12-29 at 10:29 +1300, Jerome Brown wrote: |
3 |
> > William Kilian wrote: |
4 |
> > |
5 |
> > > Apparently portage_confdir cannot be a symlink. I was using a symlink to |
6 |
> > > my /etc/portage directory. When I renamed the symlink and cp -a |
7 |
> > > /etc/portage where-symlink-was, then the contents of the files started |
8 |
> > > to matter. If there is an argument that portage_confdir shouldn't be a |
9 |
> > > symlink, my response is that building multiple targets using identical |
10 |
> > > configuration info but different (sub)archs is a strong use-case |
11 |
> > > justifying a symlink. |
12 |
> > > |
13 |
> > |
14 |
> > Wouldn't using a hard link instead work? (ln /etc/portage/ |
15 |
> > /my/build/root/etc/portage) |
16 |
> |
17 |
> You should never use a hard link on a directory. A bind mount would be |
18 |
> the preferred method of doing this. |
19 |
> |
20 |
|
21 |
A bind mount might be the best way to go about this anyway. I will |
22 |
update the code in CVS. |
23 |
|
24 |
Cheers, |
25 |
//John |
26 |
-- |
27 |
John Davis <zhen@g.o> |
28 |
The Gentoo Foundation |
29 |
Trustee | Release Engineering Manager | Catalyst code monkey |
30 |
|
31 |
--- |
32 |
"When people learn no tools of judgement and merely follow their hopes, |
33 |
the seeds of political manipulation are sown" |
34 |
- Stephen Jay Gould |