Adam C. Emerson [EMAIL PROTECTED] writes:
Well, specifically I want to remove libxine1-console. But libxine1
depends on both libxine1-console and libxine1-x specifically, rather
than as alternates.
This was indeed the idea. However, this would lead to breakage wrt
partial upgrades: Consider
Package: libxine1
Version: 1.1.8-3
Severity: wishlist
It doesn't seem quite sensible to me to split up plugins into libraries
then depend on all of them. I have no use for libxine1-console, say,
and I'd like to be able to uninstall it.
(Even better would be if libxine1-misc-plugins were split
Adam C. Emerson [EMAIL PROTECTED] writes:
It doesn't seem quite sensible to me to split up plugins into libraries
then depend on all of them. I have no use for libxine1-console, say,
and I'd like to be able to uninstall it.
There should be no problem with removing them if you don't want
On 2007-12-02 10:53 +0100, Reinhard Tartler wrote:
Adam C. Emerson [EMAIL PROTECTED] writes:
It doesn't seem quite sensible to me to split up plugins into libraries
then depend on all of them. I have no use for libxine1-console, say,
and I'd like to be able to uninstall it.
There should
On Sun, Dec 02, 2007 at 10:53:17AM +0100, Reinhard Tartler wrote:
Adam C. Emerson [EMAIL PROTECTED] writes:
It doesn't seem quite sensible to me to split up plugins into libraries
then depend on all of them. I have no use for libxine1-console, say,
and I'd like to be able to uninstall
5 matches
Mail list logo
