Re: how to submit a new module via CVS?
| From: | Andrei Zmievski | Date: | Mon, 10 Jul 2000 20:38:39 +0000 |
| Subject: | Re: how to submit a new module via CVS? | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-24124@lists.php.net to get a copy of this message | ||
On Mon, 10 Jul 2000, PHP development @echospace wrote:
> Hi, I would greatly appreciate if someone answers a few basic CVS-related questions.
>
> I am about to submit a new module (ext/pspell). I am not familiar with how CVS works, but I
> assume that something like</FONT>
>
> cvs import -m "initial release" php4/ext/pspell [vendor-tag] [release-tag]
> followed by a commit should work. The question is: what should I make those vendor-tag and
> release-tag? Do they carry any useful information in PHP tree, or I can just use whatever I want?
No. You check out PHP and then add your module under ext/. Then you do:
cvs add ext/pspell
cvs add ext/pspell/*
cvs commit
> Another question: Should I modify anything at all outside the ext/pspell directory, or is it
> somebody else's responsibility to run buildconf when they get the tree?
No, you shouldn't modify anything outside ext/pspell.
> Any yet another question. Many (but not all) source files I found in php tree contain $Id tag
> in them. Is it required or optional? And how do I create it - manually editing, or is there a tool
> that does it for me?
It's optional. When you cvs commit, $Id$ gets replaced with a CVS info
string.
> The questions might be dumb, but I am new to CVS and have to figure them out sooner rather than
> later.
No problem. Read README.CVS_RULES too in the top PHP directory.
-Andrei
* Unix is user friendly, it is just chooses its users selectively. *