Re: Depricating a library
Robert Bihlmeyer [EMAIL PROTECTED] immo vero scripsit If you want to provide further hints, upload a final version containing you can remove me without ill effects in the description. I think I would just remove the package, since the package has only entered unstable, and not on testing nor stable. On the other hand, if it had already entered testing or stable, things would have been slightly more complicated. regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer -BEGIN GEEK CODE BLOCK- Version: 3.12 GE d+ s:- a-- C+ UL P- L+++ E W++ N o-- K- w++ O- M- V-- PS+ PE-- Y+ PGP+ t-- 5 X-- R* tv- b+ DI- D++ G e h* r% !y+ --END GEEK CODE BLOCK--
Re: Depricating a library
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. :) d -- Daniel Stone[EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Depricating a library
Daniel Stone [EMAIL PROTECTED] writes: [...] and make new versions of qtecasound and evawave, that have Conflicts: libqtecasound, to make sure it gets removed from systems as well. This is overzealous unless the new versions do actually conflict with the old lib (which I assume is not the case). With that people are unnecessarily prevented from having an old version of qtecasound (needs the lib) and a new version of ecawave (conflicts with the lib) installed together. Ensuring the purge of an old library from users' machines is not the maintainer's task. Appearance of the package in dselect's obsolete/local section, and tools like deborphan should suffice. If you want to provide further hints, upload a final version containing you can remove me without ill effects in the description. -- Robbe signature.ng
Re: Depricating a library
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. :) d -- Daniel Stone[EMAIL PROTECTED] [EMAIL PROTECTED]
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 obsolete package. -S -- 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
Re: Depricating a library
Daniel Stone [EMAIL PROTECTED] writes: [...] and make new versions of qtecasound and evawave, that have Conflicts: libqtecasound, to make sure it gets removed from systems as well. This is overzealous unless the new versions do actually conflict with the old lib (which I assume is not the case). With that people are unnecessarily prevented from having an old version of qtecasound (needs the lib) and a new version of ecawave (conflicts with the lib) installed together. Ensuring the purge of an old library from users' machines is not the maintainer's task. Appearance of the package in dselect's obsolete/local section, and tools like deborphan should suffice. If you want to provide further hints, upload a final version containing you can remove me without ill effects in the description. -- Robbe signature.ng Description: PGP signature
Depricating a library
Hello, Upstram of qtecasound has depricated libqtecasound, and the only application which depended upon libqtecasound (qtecasound, and ecawave) no longer need the library. How would I handle this situation smoothly? Any ideas? 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 ? regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer -BEGIN GEEK CODE BLOCK- Version: 3.12 GE d+ s:- a-- C+ UL P- L+++ E W++ N o-- K- w++ O- M- V-- PS+ PE-- Y+ PGP+ t-- 5 X-- R* tv- b+ DI- D++ G e h* r% !y+ --END GEEK CODE BLOCK-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Depricating a library
Hello, Upstram of qtecasound has depricated libqtecasound, and the only application which depended upon libqtecasound (qtecasound, and ecawave) no longer need the library. How would I handle this situation smoothly? Any ideas? 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 ? regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer -BEGIN GEEK CODE BLOCK- Version: 3.12 GE d+ s:- a-- C+ UL P- L+++ E W++ N o-- K- w++ O- M- V-- PS+ PE-- Y+ PGP+ t-- 5 X-- R* tv- b+ DI- D++ G e h* r% !y+ --END GEEK CODE BLOCK--
