| 1 |
On Thu, Mar 29, 2018 at 11:47:21AM -0400, Michael Orlitzky wrote: |
| 2 |
> On 03/29/2018 11:28 AM, Alec Warner wrote: |
| 3 |
> > |
| 4 |
> > Is there any particular reason we need to remove them? |
| 5 |
> > |
| 6 |
> |
| 7 |
> The PMS says that empty directories are undefined, so the portage |
| 8 |
> behavior of installing them and leaving them alone leads to |
| 9 |
> incompatibilities. Ebuilds rely on the portage behavior, and if another |
| 10 |
> PM (within its rights) deletes them, then the package breaks with the |
| 11 |
> non-portage PM. |
| 12 |
|
| 13 |
Maybe so, but you just made the argument for doing nothing different in |
| 14 |
current eapis and proposing stripping empty directories in eapi 7. |
| 15 |
However, this should be stripping empty directories combined with |
| 16 |
failing the emerge. |
| 17 |
|
| 18 |
The issue is that if an upstream build system creates a directory, then |
| 19 |
the upstream software tries to access the directory without creating |
| 20 |
it, there will be runtime breakage. |
| 21 |
|
| 22 |
William |
Archives