[Cvsnt] Setup Question

[Bo Berglund]

It is entirely possible to have a "master" project and some "subprojects" within
the master project. Just create the structure you need with all subprojects in its
own folder and commit to CVS.
Then on checkout you can do this:

cvs co MasterProj   (which will get you all subprojects as well)
cvs co MasterProj/Subproj1  (will get only subproj 1)

To ease the handling further it is possible to define the subproj1 as its own module
name in the CVSROOT/modules file. Say that it is declared as SuperProj there.
cvs co SuperProj (will now check out the same as MasterProj/SubProj1)

If you want to study a masterproject with subprojects you can check out cvsgui from
sourceforge. It contains a lot of subprojects for unix, mac, windows etc.

/Bo

-----Original Message-----
From: Dieter Bogdoll [mailto:srhizogcfzsc at spammotel.com]
Sent: den 20 februari 2002 08:24
To: cvsnt at cvsnt.org
Subject: Re: [Cvsnt] Setup Question


Hi Andrew,

thanks for your tip.

But I have one little problem with it. I will get really many directories on
the same level within CVS.
All projects and sub-projects would be lying in one directory. It would be
"nicer" if they would be in
a normal directory structure where the sub-project are within the directory
of the father project.

Does nobody have similary problems?

Ciao
   Dieter

<aw_asdf.spam at me.not.yahoo.com> wrote in message
news:a4urvg$bs1$1 at sisko.my.home...
> Dieter Bogdoll <srhizogcfzsc at spammotel.com> wrote:
>
> > I want to achieve that some peoples can see the complete project with
all
> > sub-projects
> > and other people sees only one or more sub-projects.
>
> There are several ways of doing this.  Probably the easiest
> is the following:
>
> o Create a directory for each sub-project.
>     subproject_1
>     subproject_2
>   etc.  Import these into CVS.
> o Create a directory for the top-level project, but do not
>   place the subprojects into it.  Import this into CVS.
>
>   At this point, you will have the following in your CVS
>   top-level directory:
>       CVSROOT
>       main_project
>       subproject_1
>       subproject_2
>
>
> o In the modules file (use "cvs checkout CVSROOT" to get an
>   editable copy, modify it and then use "cvs commit" to get
>   the changes read) you can then place a line like the
>   following:
>     BigProject main_project &subproject_1 &subproject_2
>
> If you then check out "BigProject"
>     cvs checkout BigProject
> you will get the contents of main_project (the main project
> directory) placed in a project called "BigProject".  In this
> directory (BigProject) there will be two subdirectories
> called supbroject_1 and subproject_2.  Changes etc are managed
> on a per-directory basis, so you don't have to worry about
> "conflicts".  Both sub-projects are real entities in the CVS
> repo, so you can check them out independently.
>
> Note that if a user checks out "main_project" directly (i.e.;
> the directory, not the module), then they will _NOT_ get the
> subprojects as well.
>
> Regards,
> Andrew.
>
> _______________________________________________
> Cvsnt mailing list
> Cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt


_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt