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