Re: [PEPr] Comment on Configuration::Config_Registry
| From: | Chuck Hagenbuch | Date: | Mon, 02 Feb 2004 01:11:07 +0000 |
| Subject: | Re: [PEPr] Comment on Configuration::Config_Registry | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-25410@lists.php.net to get a copy of this message | ||
Quoting Pierre-Alain Joye <paj@pearfr.org>:
All that sounds a bit weird to me. Why not ask to release this horde module through PEAR if it is not dependent of other non pear package? Note it's only a question, I do not know this module :)It will be in a package, but PEAR has previously expressed disinterest (to say the least - disgust is closer for a lot of people) in having Horde packages that aren't completely independent of the Horde framework. Much of the benefit of the Registry:: package as it exists in Horde comes from having it know how to load configuration files, how to load user preferences, and how to make sure that a particular user is authorized to use any given application. You're not going to get that without the rest of the pieces of Horde. Speaking to a more general point, everything that you see here: http://cvsweb.horde.org/cvs.php/framework/ ... is available as a PEAR-style package. Most of what's still in: http://cvsweb.horde.org/cvs.php/horde/lib/ ... will be moved to packages before Horde 3.0 is released - we're working on it now. Some of those packages are already available through PEAR. In general we're happy to upload any of them to the PEAR package database, though they're certainly not moving to PEAR CVS. A lot of them will have dependancies on other Horde packages or on the framework itself; some of those are removeable and we actively welcome help doing that. -chuck -- Charles Hagenbuch, <chuck@horde.org> "Here, I brought some cole slaw. It's made from peeeooople! Just kidding."