Bug#681419: Alternative dependencies on non-free packages in main
Ian Jackson <email@example.com> writes:
> It seems to me that there are two possible ways to do this:
> - Somehow change the package metatdata so that the reference to the
> non-free package lives in the non-free repo.
> - Change the packager UI, websites, etc. which interpret this data
> for users to not show references to non-free when they aren't
Well, if we want to go this route, we could require use of a virtual
package in all cases like this. Then foo and foo-nonfree would both
Provide: foo (and probably Conflicts: foo), and those who want to can
enable non-free and install foo-nonfree.
That was one of the options offered in the Policy discussion.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>