-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Christian,
On 06/18/2010 10:22 AM, Christian Grobmeier wrote:
>>
>> Do not forget that we will also need a PEAR channel server. I suggest
>> that we use Pirum because it generates static XML and does not depend
>> on a database etc.
> We have the need for a PEAR channel in Log4PHP world too.
> pear.apache.org would be a good idea imho. Also, distributions should
> be made from us through official apache channels
I'm not sure, if a common PEAR channel is a good idea, since Zeta
provides quite a lot of packages and mixing these up with other projects
could be quite confusing for the users.
We previously provided the components in the following ways:
- - A bundled download package for each collective release of the library
- Containing all components of a specific release cycle
- Available as alpha/beta as soon as all components for this cycle
are ready
- - One PEAR package per component through the channel server
- Also most recent alpha/beta versions, as soon as ready
- - A meta package on the PEAR server for each bundle release
- Pulling all component packages of this bundle version
What are the requirements from Apache side for this process?
Regards,
Toby
- --
Tobias Schlitt [email protected] GPG Key: 0xC462BC14
a passion for php http://schlitt.info/opensource
eZ Components are Zeta Components now! http://bit.ly/9S7zbn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkwbY/cACgkQ5bO3TcRivBTNXgCgh6Ig9MmrfiYZGuc/CJrCbX/W
whQAn1BTFBg3H4XE++t0DkRXasYzrYpC
=sTwj
-----END PGP SIGNATURE-----
