AW: [PEAR-DEV] Protocol for deleting a package from PEAR?
| From: | Stephan Schmidt | Date: | Fri, 16 Jan 2004 16:26:32 +0000 |
| Subject: | AW: [PEAR-DEV] Protocol for deleting a package from PEAR? | ||
| References: | 1 | Groups: | php.pear.dev php.pear.qa |
| Request: | Send a blank email to pear-dev+get-25099@lists.php.net to get a copy of this message | ||
Hi,
> - a maintainer does not want to maintain a package anymore
> -> he has to post on pear-dev to ask for a new maintainer
> -> after 4 weeks and no reply the package should be deleted
> (or maybe first
> marked obsolete)
I don't think it's a good idea to delete packages you do not want to
maintain.
If someone develops an application that depends on a PEAR package and
distributes this application without the dependencies, the users of the
application need to install the PEAR packages. If you delete them, this
will totally break the application.
What would you say, if the PHP Group got bored of developing PHP and
deleted all PHP releases from php.net?
In the concrete case of Net_Dig, I think you should add a note on the
package overview page, that marks the package as deprecated and
recommends the usage of Net_DNS. Even better would be including a link
to a small tutorial that explains to to move from Net_Dig to Net_DNS.
Stephan