| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 14/01/13 09:57 AM, Zac Medico wrote: |
| 5 |
> On 01/14/2013 06:46 AM, Ian Stakenvicius wrote: |
| 6 |
>> This particular symlink was put there by openrc though, wasn't |
| 7 |
>> it? |
| 8 |
> |
| 9 |
> Yeah, openrc uses the migrate_to_run function from |
| 10 |
> /etc/init.d/bootmisc. |
| 11 |
> |
| 12 |
>> So I'd expect that on the whole this should be left for openrc to |
| 13 |
>> deal with or otherwise left to the user...? |
| 14 |
> |
| 15 |
> As things are now, the symlink is an orphan, and emerge will |
| 16 |
> automatically remove the symlink when the last package that |
| 17 |
> installed something under /var/run/ is uninstalled. |
| 18 |
|
| 19 |
...that doesn't sound good ; /var/run traditionally isn't a path used |
| 20 |
solely via src_install() but rather a path used by packages at |
| 21 |
runtime, no? If that's the case, that symlink probably should've been |
| 22 |
set up to remain until user intervention removes it.. |
| 23 |
|
| 24 |
|
| 25 |
> |
| 26 |
>> [tangent] it's a bit late for /var/run , but i wonder if, for the |
| 27 |
>> next path migration, there might be some way to account for which |
| 28 |
>> packages use the old path, say, make a list somewhere, and have |
| 29 |
>> the ebuilds remove their atom from that list as they migrate to |
| 30 |
>> the new path.. Then once the list is empty the compatibility |
| 31 |
>> symlink could be cleaned up automatically or the user notified.. |
| 32 |
>> Probably this would need to be handled via an eclass and specific |
| 33 |
>> function calls in all relevant ebuilds, as i doubt there would be |
| 34 |
>> a way to do this generically in portage itself. [/tangent] |
| 35 |
>> |
| 36 |
> |
| 37 |
> That sounds a lot like the existing behavior (automatic symlink |
| 38 |
> removal by emerge). |
| 39 |
|
| 40 |
OK i'm a little confused. Putting my earlier note aside, if the |
| 41 |
symlink will be auto-cleaned after no packages use it, what's the |
| 42 |
point/need for the original message from portage then?? Is it just QA |
| 43 |
for the ebuild maintainer? |
| 44 |
-----BEGIN PGP SIGNATURE----- |
| 45 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 46 |
|
| 47 |
iF4EAREIAAYFAlD0H68ACgkQ2ugaI38ACPC+vAEAhGHZMfN2/dY+SXHFBStbckkH |
| 48 |
9geiYEJAOEa6kcbOS28A/2hUq67WlVRiRP0vqW1WdeTod7aHhvc//q2TH994BWaI |
| 49 |
=pWiP |
| 50 |
-----END PGP SIGNATURE----- |
Archives