1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 14/01/13 10:53 AM, Zac Medico wrote: |
5 |
> On 01/14/2013 07:44 AM, Zac Medico wrote: |
6 |
>> On 01/14/2013 07:09 AM, Ian Stakenvicius wrote: |
7 |
>>> OK i'm a little confused. Putting my earlier note aside, if |
8 |
>>> the symlink will be auto-cleaned after no packages use it, |
9 |
>>> what's the point/need for the original message from portage |
10 |
>>> then?? Is it just QA for the ebuild maintainer? |
11 |
>> |
12 |
>> Unfortunately, there are a number of different possible |
13 |
>> scenarios. It may serve as QA for the ebuild maintainer. It may |
14 |
>> be triggered by a symlink that the sysadmin has manually created. |
15 |
>> In any case, there's a performance penalty, since portage has to |
16 |
>> search for other packages that installed files underneath the |
17 |
>> symlink. The performance penalty can be avoided for a given |
18 |
>> symlink by adding it to UNINSTALL_IGNORE (which makes the message |
19 |
>> useful, regardless of where the symlink originated from). |
20 |
> |
21 |
> You can measure the performance penalty for the /var/run symlink |
22 |
> by running this command: |
23 |
> |
24 |
> time portageq owners / /var/run |
25 |
> |
26 |
|
27 |
Based on the performance penalty, would it make sense then for |
28 |
system-managed symlinks like /var/run that it would be automatically |
29 |
added to |
30 |
UNINSTALL_IGNORE and its removal managed separately by whatever put it |
31 |
there in the first place?? |
32 |
|
33 |
(and additionally, that the warning wouldn't be presented to end-users |
34 |
because of it being a system-managed migration symlink instead of a |
35 |
end-user-managed one)? |
36 |
|
37 |
-----BEGIN PGP SIGNATURE----- |
38 |
Version: GnuPG v2.0.19 (GNU/Linux) |
39 |
|
40 |
iF4EAREIAAYFAlD0McYACgkQ2ugaI38ACPADjgD8D1nRkHqYNQLwtfb43X5QwAFI |
41 |
V9EM0yqdOWX9zI98+tABAJS5KTiZkejCVwK9Ord0VRtkyGVkGgZ+HDBvuOJHsIUA |
42 |
=3+S4 |
43 |
-----END PGP SIGNATURE----- |