| 1 |
On Wed, 2004-12-29 at 10:29 +1300, Jerome Brown wrote: |
| 2 |
> William Kilian wrote: |
| 3 |
> |
| 4 |
> > Apparently portage_confdir cannot be a symlink. I was using a symlink to |
| 5 |
> > my /etc/portage directory. When I renamed the symlink and cp -a |
| 6 |
> > /etc/portage where-symlink-was, then the contents of the files started |
| 7 |
> > to matter. If there is an argument that portage_confdir shouldn't be a |
| 8 |
> > symlink, my response is that building multiple targets using identical |
| 9 |
> > configuration info but different (sub)archs is a strong use-case |
| 10 |
> > justifying a symlink. |
| 11 |
> > |
| 12 |
> |
| 13 |
> Wouldn't using a hard link instead work? (ln /etc/portage/ |
| 14 |
> /my/build/root/etc/portage) |
| 15 |
|
| 16 |
You should never use a hard link on a directory. A bind mount would be |
| 17 |
the preferred method of doing this. |
| 18 |
|
| 19 |
-- |
| 20 |
Chris Gianelloni |
| 21 |
Release Engineering - Operational/QA Manager |
| 22 |
Games - Developer |
| 23 |
Gentoo Linux |
Archives