W dniu czw, 29.03.2018 o godzinie 11∶34 -0500, użytkownik William Hubbs napisał: > On Thu, Mar 29, 2018 at 12:24:38PM -0400, Michael Orlitzky wrote: > > On 03/29/2018 11:57 AM, William Hubbs wrote: > > > > > > > > The PMS says that empty directories are undefined, so the portage > > > > behavior of installing them and leaving them alone leads to > > > > incompatibilities. Ebuilds rely on the portage behavior, and if another > > > > PM (within its rights) deletes them, then the package breaks with the > > > > non-portage PM. > > > > > > Maybe so, but you just made the argument for doing nothing different in > > > current eapis and proposing stripping empty directories in eapi 7. > > > However, this should be stripping empty directories combined with > > > failing the emerge. > > > > If we strip them only in EAPI=7, then that still leaves all of these > > packages broken with respect to the PMS in the other EAPIs. > > > > Stripping the empty directories isn't my favorite approach, but leaving > > things broken looks bad on paper too. > > If we are going to strip the empty directories, we should hard fail the > emerge at the same time. Otherwise there is no way to know whether the > package we successfully install will now run. >
The developer is supposed to *look* at what the package installs. If people just commit ebuilds based on 'Portage did not explode', then maybe they shouldn't have commit access in the first place. -- Best regards, Michał Górny
