1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 14/01/13 04:44 AM, Zac Medico wrote: |
5 |
> On 01/14/2013 01:33 AM, Dirkjan Ochtman wrote: |
6 |
>> I've seen this pop up a lot recently: |
7 |
>> |
8 |
>> * One or more symlinks to directories have been preserved in |
9 |
>> order to * ensure that files installed via these symlinks remain |
10 |
>> accessible. This * indicates that the mentioned symlink(s) may be |
11 |
>> obsolete remnants of an * old install, and it may be appropriate |
12 |
>> to replace a given symlink with * the directory that it points |
13 |
>> to. * * /var/run * |
14 |
>> |
15 |
>> This might just be me being dense, but this doesn't seem very |
16 |
>> actionable to me. Who should replace the given symlink with the |
17 |
>> directory that it points to, the user or the package maintainer? |
18 |
> |
19 |
> It depends on who created the symlink in the first place, and |
20 |
> whether or not the symlink is still desirable. Unfortunately, there |
21 |
> are a number of possible scenarios. |
22 |
> |
23 |
> You probably want to keep that /var/run symlink, at least until all |
24 |
> of your installed packages have been fixed to use /run directly. |
25 |
> You can suppress the warning by putting a setting like this in |
26 |
> make.conf: |
27 |
> |
28 |
> UNINSTALL_IGNORE="${UNINSTALL_IGNORE} /var/run" |
29 |
> |
30 |
> That will prevent portage from trying to uninstall that symlink. |
31 |
> |
32 |
>> And where should it be replaced? In ebuild code? |
33 |
> |
34 |
> It's possible for ebuild code to do it, if appropriate for the |
35 |
> given scenario. For example, the skype ebuild removes an obsolete |
36 |
> "${EROOT}"/usr/share/${PN} symlink in pkg_preinst. |
37 |
|
38 |
|
39 |
This particular symlink was put there by openrc though, wasn't it? So |
40 |
I'd expect that on the whole this should be left for openrc to deal |
41 |
with or otherwise left to the user...? |
42 |
|
43 |
[tangent] |
44 |
it's a bit late for /var/run , but i wonder if, for the next path |
45 |
migration, there might be some way to account for which packages use |
46 |
the old path, say, make a list somewhere, and have the ebuilds remove |
47 |
their atom from that list as they migrate to the new path.. Then once |
48 |
the list is empty the compatibility symlink could be cleaned up |
49 |
automatically or the user notified.. Probably this would need to be |
50 |
handled via an eclass and specific function calls in all relevant |
51 |
ebuilds, as i doubt there would be a way to do this generically in |
52 |
portage itself. |
53 |
[/tangent] |
54 |
-----BEGIN PGP SIGNATURE----- |
55 |
Version: GnuPG v2.0.19 (GNU/Linux) |
56 |
|
57 |
iF4EAREIAAYFAlD0GjkACgkQ2ugaI38ACPD5rwD/f4MkzFrlSShRWt/9WB12kybX |
58 |
uY0uzf5SFmfihzNthOABALr6bT3bB7PAr4eh4tmQH+jH9Z635OD5/BcdJBYw7tLl |
59 |
=S5ML |
60 |
-----END PGP SIGNATURE----- |