Hi Paul On Thu, 30 Aug 2018 12:03:31 +0200 Paul Gevers <firstname.lastname@example.org> wrote: > I have just pushed commit 9fade8dcb501250f704da9c77af1f8e6165dc941 that > documents that we want to remove the needs-recommends option as we > discussed in https://lists.debian.org/debian-ci/2018/06/msg00016.html. So I have this specific case where I found needs-recommends quite convenient: I have a package (firewalld) which has optional dependencies like ipset or ebtables. If those are not installed, firewalld will log a warning and continue with the functionality disabled. I want to ship two autopkgtests: One with recommends installed, in which case no errors and warnings are allowed in the log. One without recommends installed, in which case errors are not allowed in the log, but warnings are. Now, if needs-recommends is going to be deprecated/removed, I'll have to specify the Recommends twice: once in debian/tests/control and debian/control and I don't like this duplication as this is prone to get out-of-sync. Just wanted to provide a data point why it might be useful to keep needs-recommends. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Description: OpenPGP digital signature