1.1

On Wed, 2004-12-29 at 10:03 -0500, Chris Gianelloni wrote:
> On Wed, 2004-12-29 at 10:29 +1300, Jerome Brown wrote:
> > William Kilian wrote:
> > 
> > > Apparently portage_confdir cannot be a symlink. I was using a symlink to 
> > > my /etc/portage directory. When I renamed the symlink and cp -a 
> > > /etc/portage where-symlink-was, then the contents of the files started 
> > > to matter. If there is an argument that portage_confdir shouldn't be a 
> > > symlink, my response is that building multiple targets using identical 
> > > configuration info but different (sub)archs is a strong use-case 
> > > justifying a  symlink.
> > > 
> > 
> > Wouldn't using a hard link instead work? (ln /etc/portage/ 
> > /my/build/root/etc/portage)
> 
> You should never use a hard link on a directory.  A bind mount would be
> the preferred method of doing this.
> 

A bind mount might be the best way to go about this anyway. I will
update the code in CVS.

Cheers,
//John
-- 
John Davis <zhen@g.o>
The Gentoo Foundation
Trustee | Release Engineering Manager | Catalyst code monkey

---
"When people learn no tools of judgement and merely follow their hopes,
the seeds of political manipulation are sown"
- Stephen Jay Gould