| 1 |
On 01/10/2018 03:55 PM, Zac Medico wrote: |
| 2 |
>> |
| 3 |
>> This is going to break a lot of packages whose build systems create e.g. |
| 4 |
>> /var/lib/foo and do nothing with it immediately. The ebuild should be |
| 5 |
>> calling keepdir on those paths, but how would anyone know that? |
| 6 |
> |
| 7 |
> If we consider that portage already removes these directories if they |
| 8 |
> are still empty when the package is re-merged or upgraded, then maybe |
| 9 |
> the risk is low enough? |
| 10 |
> |
| 11 |
|
| 12 |
Does it? (Are we talking about the same thing?) |
| 13 |
|
| 14 |
For example, the nagios-core build system creates a bunch of empty |
| 15 |
directories under /var/nagios: |
| 16 |
|
| 17 |
$ find /var/nagios |
| 18 |
/var/nagios |
| 19 |
/var/nagios/rw |
| 20 |
/var/nagios/home |
| 21 |
/var/nagios/spool |
| 22 |
/var/nagios/spool/checkresults |
| 23 |
/var/nagios/archives |
| 24 |
|
| 25 |
Re-emerging the same version of nagios-core doesn't kill them off. |
Archives