Re: PEAR 1.3b3 problems

Hi, Alan Knowles wrote:

<depreciates>DB</depreciates> or <replaces>DB</replaces>

I would prefer <replaces> as the term we look for is deprecate - depreciate is to lower financial value here in US, don't know if that is a US-ism or not, but the ambiguity between the two spellings might cause lots of problems in the future.

obviously the trickery on pearweb is a bit nasty Thinking out loud.. a) flag packages as depreciated, with the name of the new package. b) have a new package record for the new replacement. c) store the old package name in an extra field in the package description. d) ignore depreciated from the browse pages e) on DB2's page just show a link saying Used to be called _DB_ (with a link to that package page..) f) on DB's page show a bit warning (as it's flagged depreciated) and what it's depreciated by. g) on search results indicate that something is depreciated..

Looks pretty good.

While it doesnt quite follow the line of keeping one 'package page', for a major new version. - I think that the implementaiton of this may be a little problematic.. (and as long as it's clear that there is a connection between the two, I dont think it's going to throw people too much..)

agreed

As far as downloading.. - It may add a little complexity.. - as the download of the old package tgz file should expect a warning (eg. this is depreciated) + try again??? with ?warning_issued=yes...

I think a simple warning will be enough. In other words, once a package has been deprecated, we should force people to use --force $ pear install DB Error: DB is deprecated in favor of DB2, use --force if you are sure you want DB $ pear install DB2 for most users that will work, others can simply: $ pear install --force DB Warning: DB is deprecated in favor of DB2 Regards, Greg