| 1 |
>>>>> On Sun, 12 Nov 2017, Michael Orlitzky wrote: |
| 2 |
|
| 3 |
> Some day -- I'll add it to my list. For now I'll update the docs to |
| 4 |
> explain why you should use keepdir, and do a QA warning for empty |
| 5 |
> directories. Then how does this sound for EAPI=next? |
| 6 |
|
| 7 |
> * Ban keepdir. |
| 8 |
|
| 9 |
> * Have portage call its keepdir code on any empty directories in $D |
| 10 |
> between src_install and pkg_preinst. |
| 11 |
|
| 12 |
> * Update the devmanual and portage documentation to suggest dodir |
| 13 |
> instead of keepdir in the new EAPI. |
| 14 |
|
| 15 |
> * Change the PMS to remove "undefined behavior" and replace it with |
| 16 |
> "empty directories must be tracked, and may only be removed once no |
| 17 |
> installed package is using them," or something along those lines. |
| 18 |
> That leaves the implementation up to the PM. |
| 19 |
|
| 20 |
How? Look up VDB entries of all installed packages? Note that this |
| 21 |
would have to be done for every dir that becomes empty, not just the |
| 22 |
ones currently containing a .keep_* file. |
| 23 |
|
| 24 |
What problem are you trying to solve? I see typically around 100 |
| 25 |
.keep_* files on my systems. These are empty files, so they don't use |
| 26 |
any blocks. And 100 inodes system wide looks like negligible usage |
| 27 |
of resources to me. |
| 28 |
|
| 29 |
Ulrich |
Archives