Re: Depricating a library
On Mon, Jun 18, 2001 at 05:02:12PM +1000, Daniel Stone wrote:
> On Mon, Jun 18, 2001 at 10:49:35AM +0900, Junichi Uekawa wrote:
> > Hello,
> > Upstram of qtecasound has depricated libqtecasound,
> > and the only application which depended upon libqtecasound (qtecasound, and ecawave)
> > no longer need the library.
> > Would I need to make an empty package of libqtecasound to ensure
> > it no longer exists, or do I make newer version of ecawave and qtecasound
> > to Conflicts: with them, or do I just leave them there ?
> Since the only apps that used to depend on it, now no longer need it, file a
> bug against ftp.d.o asking for libqtecasound to be removed from the
> archives, and make new versions of qtecasound and evawave, that have
> Conflicts: libqtecasound, to make sure it gets removed from systems as well.
Surely removing the library from the archives is enough. Dselect will
then show it as "obsolete".
Making two packages artificially conflict with the obsolete lib seems
obnoxious. Leave it to the local admin to decide what to do with an
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants