| 1 |
Jerome Brown wrote: |
| 2 |
|
| 3 |
> William Kilian wrote: |
| 4 |
> |
| 5 |
>> Apparently portage_confdir cannot be a symlink. I was using a symlink |
| 6 |
>> to my /etc/portage directory. When I renamed the symlink and cp -a |
| 7 |
>> /etc/portage where-symlink-was, then the contents of the files |
| 8 |
>> started to matter. If there is an argument that portage_confdir |
| 9 |
>> shouldn't be a symlink, my response is that building multiple targets |
| 10 |
>> using identical configuration info but different (sub)archs is a |
| 11 |
>> strong use-case 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 |
> |
| 18 |
Are hard links advisable for directories? I would think so, but ln |
| 19 |
complains about them on directories so I avoid them. |
| 20 |
|
| 21 |
William Kilian |
| 22 |
|
| 23 |
-- |
| 24 |
gentoo-catalyst@g.o mailing list |
Archives