Re: Use CVS while still drafting?

On 4/18/06, Jacob Singh <jacob@calabashmusic.com> wrote: > Thanks for the clarification, > > If I was going to offer svn access on my machine, what is best practices > for dependencies, etc. > > Should I create repo that has all the required PEAR packages in it and > put my package where it will eventually belong? So people end up > checking out everything? > > The issue is that all my include statements obviously start from the > pear install root. So letting someone just checkout my package, will > not be very useful. On the other hand, including everything pear seems > counterintuitive because it will create a separate pear dir on the > developer's box... > No, don't check everything into your repository. People should be installing PEAR packages normally. Have them install the deps, then check out your code for development. Remember you can always set up a package.xml to deal with deps and all without having your package actually *in* PEAR. > Any suggestions? > -J > > Daniel Convissor wrote: > > Hi Jacob: > > > >> So is it impossible to use the facilities (CVS, shell, etc) on the > >> pear.php.net site for collaboration until the code is at alpha and gets > >> accepted? > > > > The cvs.php.net repository isn't generally used for this role. There > > isn't shell access for general users. People usually put up .phps files > > and tar balls on a web server somewhere. > > > > --Dan > > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Justin Patrin