| 1 |
William Kilian wrote: |
| 2 |
|
| 3 |
> Apparently portage_confdir cannot be a symlink. I was using a symlink to |
| 4 |
> my /etc/portage directory. When I renamed the symlink and cp -a |
| 5 |
> /etc/portage where-symlink-was, then the contents of the files started |
| 6 |
> to matter. If there is an argument that portage_confdir shouldn't be a |
| 7 |
> symlink, my response is that building multiple targets using identical |
| 8 |
> configuration info but different (sub)archs is a strong use-case |
| 9 |
> justifying a symlink. |
| 10 |
> |
| 11 |
|
| 12 |
Wouldn't using a hard link instead work? (ln /etc/portage/ |
| 13 |
/my/build/root/etc/portage) |
| 14 |
|
| 15 |
|
| 16 |
-- |
| 17 |
Jerome Brown |
| 18 |
Technology Integrator |
| 19 |
Hub.Net |
| 20 |
|
| 21 |
P: +64 3 961-5116 |
| 22 |
M: +64 29 453 7663 |
| 23 |
F: +64 3 961-5129 |
| 24 |
E: jerome@××××××××××××.nz |
| 25 |
W: http://www.concepts.net.nz/ |
| 26 |
O: Level 4, 818 Colombo St, Christchurch, New Zealand |
| 27 |
S: PO Box 1879, Christchurch, New Zealand |
| 28 |
-- |
| 29 |
gentoo-catalyst@g.o mailing list |
Archives