The usual approach is to upload an empty package that Depends: on the new one and make a note in docs and/or the description...
On Fri, Apr 27, 2001 at 07:27:55PM -0500, Ashley Clark <[EMAIL PROTECTED]> spake forth: > I have a package that has been merged with another. I would like to > remove the package from the archive but I'm concerned with users that > already have the package installed. How to make sure that they know to > install another package? Upload a new version that Depends on the > replacement package, noting that it can then be deleted seems to be the > best way, but what is recommended? > > Please cc as I don't subscribe to this list. > > -- > hacker sally -- Mike Markley <[EMAIL PROTECTED]> GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084 It [being a Vulcan] means to adopt a philosophy, a way of life which is logical and beneficial. We cannot disregard that philosophy merely for personal gain, no matter how important that gain might be. - Spock, "Journey to Babel", stardate 3842.4
