| 1 |
On Sat, Dec 24, 2005 at 02:22:06AM +0900, Jason Stubbs wrote: |
| 2 |
> Symlinks are handled within portage differently to regular files. Regular |
| 3 |
> files get an mtime check and are removed if it matches. Symlinks don't get an |
| 4 |
> mtime check (even thought the mtime is stored) and are only removed if the |
| 5 |
> symlink's target doesn't exist. Hence, it seems to be this way by design. Why |
| 6 |
> it's this way? Who knows. It's been that way for longer than anyone can |
| 7 |
> remember which is why _it's so important that bugs get filed_. |
| 8 |
|
| 9 |
Honestly, I thought it was supposed to be like that, since |
| 10 |
collision-protect also doesn't protect against packages overwriting |
| 11 |
each other's symlinks (package A and package B can both create |
| 12 |
/dummy -> bin without any problems from portage). Do you want a bug |
| 13 |
report for that? |
Archives