On Tue, 6 Apr 2021 at 14:04, Ansgar <ans...@43-1.org> wrote: > > On Fri, 26 Mar 2021 22:12:33 +0000 Dimitri John Ledkov wrote: > > I don't know what is the correct process to follow here. For example, > > could the 5.32 things be promoted from modules to perl-base? > > What gets included in the (essential) perl-base package is decided by > Debian. > > I think it would be a fair request to ask for usrmerge's dependencies > to be included there if we install usrmerge by default on upgrades to > covert existing systems. The dependencies could probably be dropped > again for bookworm+1 (with perl-base having `Breaks: usrmerge (<< X)` > where `X` is the version of usrmerge depending on perl instead of perl- > base again). > > For this to work, usrmerge would need to stop using "libfile-find-rule- > perl" as well as that depends on the full "perl" package.
All of the above is very interesting, especially in the context of how Debian should approach installing / converting to usrmerge by default on upgrades. In Ubuntu, I have left usrmerge package as is. Instead of making ubuntu-minimal metapackage depend on usrmerge, I made it recommend it only. This way on upgrades, it will be installed by default. And it is also allowed to remove it after the install. And I have adjusted Ubuntu's debootstrap to always create things with merged usr, without installing usrmerge package. The remaining piece is to remove usrmerge, if conversion was successful. I am pondering if `usrmerged` package might still be a good idea, which is an empty package that fails to install if the system is not usrmerged. That way essential packages can predepend on that, once split-usr systems are no longer supported. -- Regards, Dimitri.
