Now that libsnack2 has been renamed to tcl-snack and that libsnack2-alsa has been renamed to tcl-snack-alsa, the situation seems even worse.
Is there any way a package using snack can depend on a generic version of
snack, without listing all possible backends? (i.e., depend on a generic
version that other
backends also provide?)
Bests,
Giulio.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
