Re: Requiring SCM

On Tue, 29 Mar 2005 09:08:53 -0500 chuck@horde.org (Chuck Hagenbuch) wrote: > Quoting Pierre-Alain Joye <pierre@dotgeek.org>: > > > PEAR packages must have a public CVS, I tend to want it in the > > cvs.php.net/pear repository but cannot be a requirement. > > Strongly against. I'd rather just require that packages be in > cvs.php.net CVS than see this requirement; it puts a high burden > on developers. Must have own server and hosting, etc. Of course > with channels there isn't much of a reason anymore to put up with > this kind of micromanagement - but I still think it's a mistake. Please rephrase, I miss what are your objections :) or is it simply that you do not want to have public SVC as requiremnts for PEAR packages? I rephrase mine (just in case): I would like to force people to use a public sources versions control system for any package available through PEAR. This SVC can be cvs or other as far as it is publically available. We provide a SVC (using cvs softwares) under cvs.php.net/pear as a convenience and recommanded solution. Feel free to use it _or_ not. --Pierre