Re: pecl cvs commits
| From: | Justin Hannus | Date: | Mon, 13 Sep 2004 14:25:51 +0000 |
| Subject: | Re: pecl cvs commits | ||
| References: | 1 2 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-1325@lists.php.net to get a copy of this message | ||
Thanks....very helpful. I guess that's why they call you the king? ;)
"Wez Furlong" <kingwez@gmail.com> wrote in message
news:4e89b42604091307153c8f0322@mail.gmail.com...
> First thing to do is read the "CVS Book"
> (http://cvsbook.red-bean.com/) to brush up on your CVS know-how (you
> seem to be a little confused about the difference between a branch and
> a module).
>
> Second thing is to never use "cvs import" with PHP CVS.
>
> Once you're ready, you should do something like this (generic
instructions):
>
> cvs -d:pserver:username@cvs.php.net:/repository co pecl
> cd pecl
> cp -r /path/to/your/code name-of-ext
> cvs add name-of-ext
> cd name-of-ext
> cvs add <files to go into cvs>
> cvs commit
>
> This will add your extension under pecl/name-of-ext to the HEAD branch.
> Make sure that you don't add any generated files into CVS (run "phpize
> --clean" before you "cvs commit")
>
> --Wez.
>
> On Mon, 13 Sep 2004 09:48:28 -0400, Justin Hannus
> <jhannus@visualconceptsinc.com> wrote:
> > Which branch do extension authors commit their ext too when ready? And
is
> > there anything specific to the php cvs repository that new extension
authors
> > (like myself) should know before committing?
> >
> > While browsing the tree I found branches: pear, php-src, php5,
php-doc-* --
> > but no pecl. The pear looks like a good place but I didn't really see
any
> > pecl extensions in there.
> >
> > -Justin
> >
> > --
> > PECL development discussion Mailing List (http://pecl.php.net/)
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
> >