New package: mod_suphp

[Michael Schwendt]

On Thu, 30 Jun 2005 22:26:28 +0200 (CEST), Andreas Thienemann wrote:

> Something else.
> I asked on IRC, but I didn't quite understand the reason there. I can see 
> the commited package in rpms/mod_suphp but there is nothing in 
> /devel/mod_suphp. Is this normal behaviour?

Every package is a separate module within CVS. Initial import creates the
module in the repository $CVSROOT/rpms/$name. Branches for older
distributions (FC-4, FC-3, ...) are not CVS-branches, but also modules,
with their repository root being a branch-directory within 
$CVSROOT/rpms/$name/$branch.

"cvs co devel/mod_suphp" works just fine to get the devel branch
directory. "cvs up" would not be enough to make the new module "mod_suphp"
appear.

You would need at least "cvs up -d" to make new modules appear within
an older checkout of a branch.

"cvs co rpms/mod_suphp" or "cvs co mod_suphp" gets the complete module
directory including the branch directories within it, which are modules
themselves ("cvs co mod_suphp-FC-4-dir").

-- 
Michael Schwendt <mschwendt at users.sf.net>
Fedora Core release 4 (Stentz) - Linux 2.6.12-1.1385_FC4
loadavg: 1.01 1.04 1.03