| 1 |
On 01/14/2013 06:46 AM, Ian Stakenvicius wrote: |
| 2 |
> This particular symlink was put there by openrc though, wasn't it? |
| 3 |
|
| 4 |
Yeah, openrc uses the migrate_to_run function from /etc/init.d/bootmisc. |
| 5 |
|
| 6 |
> So |
| 7 |
> I'd expect that on the whole this should be left for openrc to deal |
| 8 |
> with or otherwise left to the user...? |
| 9 |
|
| 10 |
As things are now, the symlink is an orphan, and emerge will |
| 11 |
automatically remove the symlink when the last package that installed |
| 12 |
something under /var/run/ is uninstalled. |
| 13 |
|
| 14 |
> [tangent] |
| 15 |
> it's a bit late for /var/run , but i wonder if, for the next path |
| 16 |
> migration, there might be some way to account for which packages use |
| 17 |
> the old path, say, make a list somewhere, and have the ebuilds remove |
| 18 |
> their atom from that list as they migrate to the new path.. Then once |
| 19 |
> the list is empty the compatibility symlink could be cleaned up |
| 20 |
> automatically or the user notified.. Probably this would need to be |
| 21 |
> handled via an eclass and specific function calls in all relevant |
| 22 |
> ebuilds, as i doubt there would be a way to do this generically in |
| 23 |
> portage itself. |
| 24 |
> [/tangent] |
| 25 |
> |
| 26 |
|
| 27 |
That sounds a lot like the existing behavior (automatic symlink removal |
| 28 |
by emerge). |
| 29 |
-- |
| 30 |
Thanks, |
| 31 |
Zac |
Archives