channels update
| From: | Greg Beaver | Date: | Sat, 15 May 2004 17:28:02 +0000 |
| Subject: | channels update | ||
| Groups: | php.pear.core | ||
| Request: | Send a blank email to pear-core+get-320@lists.php.net to get a copy of this message | ||
Hi,
I've completed about 95% of the channels code, installer-side.
Things left to do are:
- implement protocol checking client-side (check that xml-rpc functions are available, or download functionality, without internet query)
- implement channel verification (download package Y from channel X, make sure package Y's package.xml says it is from channel X, so no hidden attacks are possible by overwriting existing packages from other channels)
- revamp infoFrom* methods so that they can use a PEAR_Registry to check custom package name regex
- mirrors support in code. Support is in channel.xml only currently
- all web/gtk frontend code
Things already done:
- all backend code for registry, config, installation, dependencies
- all CLI frontend code
- code for updating channels list from pear.php.net (untested for obvious reasons)
- code for local channel addition/deletion
- informational code (pear channel-info, list-channels, list <channel-name>)
- package.xml and channel.xml parsing/verification/writing
Some tasks left over from PEAR 1.3
- fix error messages relating to preferred_state to be more helpful
- other minor bugs in PEAR_ErrorStack and others
This is a huge undertaking. I'll be continually refining things over the next week along with Pierre-Alain.
As soon as the issues with channel verification, infoFrom* and protocol checking are resolved, a private devel version will be made available for people to test things prior to cvs commit.
Greg