[ Thanks for this. Awesome work! ] El 10/4/25 a las 11:43, Helmut Grohne escribió:
My thinking here was to reduce the annoyance for users by degrading the dependency softly. I was told that some users expect to be able to build perl extensions without installing libperl-dev (which is why libperlVER contains the headers that #include <crypt.h>). If we were right dropping the dependency, libcrypt-dev could be automatically be removed from those systems and we'd get angry bug reports. Going to Recommends is a means to limit the annoyance while still meeting the original goal.
On the other hand: - A recommends will only have some effect for people not having libcrypt-dev installed yet, so people upgrading from trixie to forky who have both libc6-dev and libcrypt-dev installed will not see the libcrypt-dev package mysteriously removed from their systems. - In general, Debian users are already aware that all sorts of breakage in unstable is expected to happen shortly after a stable release, so I would not really expect angry bugs about this from users. So, I agree with Marco that Recommends is not necessary. For the purposes of being nice to people, I would maybe extend the period where the bugs are not RC as necessary so that we don't introduce a lots of RC bugs at once (i.e. raise to serious not in a date-based scheme but when the number of bugs is low enough). Thanks.
