| 1 |
On 11/11/2017 02:26 PM, Michał Górny wrote: |
| 2 |
>> |
| 3 |
>> As far as the actual implementation goes, I'm not sure that |
| 4 |
>> automatically-generated ".keep" files are better than having the package |
| 5 |
>> manager maintain its own database. The latter would be more complex, but |
| 6 |
>> would avoid littering everyone's filesystems with ".keep" files. |
| 7 |
> |
| 8 |
> Do you care enough to spec this properly, introduce EAPI-conditional |
| 9 |
> behavior for it and prepare patches for the package managers? |
| 10 |
> |
| 11 |
|
| 12 |
Some day -- I'll add it to my list. For now I'll update the docs to |
| 13 |
explain why you should use keepdir, and do a QA warning for empty |
| 14 |
directories. Then how does this sound for EAPI=next? |
| 15 |
|
| 16 |
* Ban keepdir. |
| 17 |
|
| 18 |
* Have portage call its keepdir code on any empty directories in $D |
| 19 |
between src_install and pkg_preinst. |
| 20 |
|
| 21 |
* Update the devmanual and portage documentation to suggest dodir |
| 22 |
instead of keepdir in the new EAPI. |
| 23 |
|
| 24 |
* Change the PMS to remove "undefined behavior" and replace it with |
| 25 |
"empty directories must be tracked, and may only be removed once no |
| 26 |
installed package is using them," or something along those lines. |
| 27 |
That leaves the implementation up to the PM. |
Archives