Re: Bug#681419: Alternative dependencies on non-free packages in main
On Fri, Jul 13, 2012 at 05:09:12PM -0600, Bdale Garbee wrote:
> Ian Jackson <email@example.com> writes:
> > I think this is a real problem. In general people sometimes find that
> > they need to enable non-free for some particular reason (perhaps even
> > just too make their nic work or something). That shouldn't mean
> > that their system becomes tainted willy-nily with non-free stuff.
> I completely agree.
The current solution to this is pinning. But ...
Currently the repository only has 2 types in the Release file: Automatic
yes and no. Maybe it is time to add a third that would cause frontends to
avoid installing any new package of that type and ask before installing
if they must to resolve some dependency conflict.