Re: PEAR Midgard wrapup

From: Date: Thu, 01 May 2003 17:56:38 +0000
Subject: Re: PEAR Midgard wrapup
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-15759@lists.php.net to get a copy of this message
On Wed Apr 30, 2003 at 10:2147PM +1200, Martin Langhoff wrote: > It was suggested that Midgard belongs to PECL, but that seems to be > targetted for C modules. I have not been able to find the PECL > guidelines either, so I am not sure if this is accurate. That's right. PECL is for PHP extensions written in C. Putting Midgard there is nonsense. > Of course, we can serve our packages from our servers -- we don't even > need a repository as the pear tools will take a valid URL, get the > package, and install it. However, this negates many advantages, > including dependance resolution, publicity (just by being alongside in > the same repository), search functionality, etc. IMO using a own server is *the* way to go for projects like Horde, Midgard et al. Actually this prevents us from running into trouble with redundant packages: I suspect that both Horde and Midgard do have their own Template or Authentation classes. Adding them to PEAR will be no good, as our focus is to reduce redundant packages to a minimum. Having those classes on a your own server instead seems to be no problem. I'm pretty sure that we can find a decent way to add links to prominent places (like http://pear.php.net/packages.php) pointing to other "PEAR servers" like pear.horde.org or migard-project.org. Concering dependencies: Dependencies towards PEAR packages can also be resolved, when one installs (Midgard|Horde) packages from another server. -- - Martin Martin Jansen http://martinjansen.com/

« previous php.pear.dev (#15759) next »