On Fri, Jan 26, 2018 at 08:01:59PM -0500, Jeremy Bicha wrote: > On Fri, Jan 26, 2018 at 7:46 PM, Santiago Vila <sanv...@unex.es> wrote: > > If you still think this is wrong you should suggest an alternative way > > to give users the freefom to remove those directories. > > There was a proposal in the original #888243 bug for that,
Yes, the report suggested an extra package, but that's overkill. > although I > don't see much benefit in giving the people the freedom to remove > these directories. But I do. The FHS only requires those directories to exist in a newly installed system. base-files ensures that those directories exist in a newly installed system. There are also other directories like /mnt or /media which are also required by FHS and are also handled in exactly the same way (i.e. created by postinst in the very first install), but they have never made piuparts to complain because nobody was brave enough to violate the FHS to the point of having files in /mnt or /media. If you want those directories to exist at *all* times, not just in a newly installed system, that would be only a personal preference, but it would not be a FHS requirement anymore. > > Otherwise, I will also respectfully disagree and will close this bug > > again. > > Could you not be so quick to close this bug? Sure. Could you not be so quick to reopen it in the first place? > Because of the piuparts > regression, chrome-gnome-shell and all its recursive dependencies > (like debian-edu) won't migrate to testing. A simple "mkdir -p /etc/opt" in postrm would restore the directory and make piuparts happy again. That would be simple and effective, and it's what I would do. Another option would be to support Firefox and Chromium only and create a different package in contrib for Chrome. Thanks.
