CVS How?

hepburnenthorpe · 06-04-2007, 08:05 PM

I'm currently playing around with my own custom LFS system. I would like to be able to commit any changes I make to a cvs repo (Ive already got a cvs server on another machine on my network)I'm just not too sure how I can go about it.

Basically what I want to do is make the / of my LFS the working directory. Of course however, I don't want to have to commit the entire OS to cvs, just any files I make changes too. This could be anything from config changes within /etc, right through to entire applications (scripts) I may write and place wherever.

How would a normal distro go about setting up a cvs as such? Ideally, Ide like to boot into LFS, checkout the project. Work on any file I like, when I'm done with that file, commit it.

Anyone else done anything like this?

Any pointers / tutorials would be most appreciated.

alunduil · 06-04-2007, 08:50 PM

If you really want to go the CVS route there are plenty of howtos here, but I would recommend switching to subversion. They have an excellent book available online.

Regards,

Alunduil

hepburnenthorpe · 06-04-2007, 09:52 PM

Um... I know how to use cvs. I'm just not exactly sure how to go about setting it up in such a way that the / of my LFS system becomes my working directory without having to import the entire OS.

hepburnenthorpe · 06-05-2007, 03:52 AM

Ok... so I'm thinking I might just be able to do this.

Code:

mkdir tmp
cd tmp
mkdir etc bin var
cvs import -m 'initial layout' mylinux thorpe r_1
cd
rm -fr tmp

Then...

Code:

cvs checkout -d / mylinux

commit only commits files Ive applied add on right? I just don't want my whole / directory added to cvs.

Would this work?

hepburnenthorpe · 06-06-2007, 08:39 AM

Now to my next problem. The above, it seems will only work if I'm root. Obviously I want to be able to checkout and commit without being root.

Has anyone got ANY advice about what I'm trying to do here? I'm just not getting anywhere here.

Dark_Helmet · 06-12-2007, 12:22 AM

I think you're living dangerously. My approach would be:

have a regular user checkout the "environment" to their home directory
make changes
do a chroot into the changed environment to test the change
commit the changes if the testing went well
execute a "publish" script that exports the cvs module to the root directory (via sudo permissions) -OR- do the export manually as root

It's the "safest" way of doing this that I've come up with. It can be a pain if the changes are not easily tested from a chroot environment (like Apache config changes), but there's certainly less risk of messing up the system because you're not working on top of a live system.