You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Christian Hammers <ch...@lathspell.de> on 2009/10/11 23:38:49 UTC
PEAR Repository for Apache projects?
Hello
Over at the log4php incubator project we are planning our first release
and thought about offering our package via a PEAR repository as well.
As you have PHP code as well, we wondered if you have already discussed
setting up something like pear.apache.org. If so, did you already got
feedback from the project mentors?
Technically such a pear repository is only an Apache VHost with some
static xml metadata files next to the .tgz packages and one admin.php
which is used to generate the metadata files when new packages are
uploaded. The admin.php needs a database, MySQL is fine, sqlite might
work as well.
bye,
-christian-
Re: PEAR Repository for Apache projects?
Posted by Chris Chabot <ch...@google.com>.
Hey Christian,
Setting up an apache pear repo sounds like a great plan, but I'm not
entirely sure shindig would fit in well since it's quite a large project
that does things like rendering gadgets, implements RESTful and JSON-RPC
API's and takes quite a bit of custom code to integrate into your (social)
site.
In my mind pear is much more library focused, and while shindig is something
you would add to an existing site, calling it a 'library' would be taking a
lot of liberty with the concept :)
-- Chris
On Sun, Oct 11, 2009 at 10:38 PM, Christian Hammers <ch...@lathspell.de> wrote:
> Hello
>
> Over at the log4php incubator project we are planning our first release
> and thought about offering our package via a PEAR repository as well.
>
> As you have PHP code as well, we wondered if you have already discussed
> setting up something like pear.apache.org. If so, did you already got
> feedback from the project mentors?
>
> Technically such a pear repository is only an Apache VHost with some
> static xml metadata files next to the .tgz packages and one admin.php
> which is used to generate the metadata files when new packages are
> uploaded. The admin.php needs a database, MySQL is fine, sqlite might
> work as well.
>
> bye,
>
> -christian-
>
Re: PEAR Repository for Apache projects?
Posted by Chris Chabot <ch...@google.com>.
Hey Christian,
Setting up an apache pear repo sounds like a great plan, but I'm not
entirely sure shindig would fit in well since it's quite a large project
that does things like rendering gadgets, implements RESTful and JSON-RPC
API's and takes quite a bit of custom code to integrate into your (social)
site.
In my mind pear is much more library focused, and while shindig is something
you would add to an existing site, calling it a 'library' would be taking a
lot of liberty with the concept :)
-- Chris
On Sun, Oct 11, 2009 at 10:38 PM, Christian Hammers <ch...@lathspell.de> wrote:
> Hello
>
> Over at the log4php incubator project we are planning our first release
> and thought about offering our package via a PEAR repository as well.
>
> As you have PHP code as well, we wondered if you have already discussed
> setting up something like pear.apache.org. If so, did you already got
> feedback from the project mentors?
>
> Technically such a pear repository is only an Apache VHost with some
> static xml metadata files next to the .tgz packages and one admin.php
> which is used to generate the metadata files when new packages are
> uploaded. The admin.php needs a database, MySQL is fine, sqlite might
> work as well.
>
> bye,
>
> -christian-
>