P is for Practical | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Hi,
Thanks for the feedback.
I did look into VCS support, and went over their mailing list archive. First of all - it is very quiet there. Second - it gives no information except "look at our examples". Well - I looked into them, and they work with a copy, after cehckout. Now to the question - do I understand CVS, because if I do understand why won't I "checkout" before I start to work. Well, let's just say I know CVS well enough. If you will look into cvsweb for example, or Apache::CVS, they both work direcrly with the CVS repository, and whenever they can't - they immitate a working directory or do some "magic" to solve this problem (look into cvsweb doAnnotate, for example, where they use cvs server command). The reasons I need a direct work with a repository are complicated (maybe another message...), but in the bottom line I need to keep live and updated branches (around 4 branches) that weight 200MB each on more then 20 machines. Just keeping a copy of all of the branches on every machine will be a headache. What I currently try to do is to immitate Apache request. If I will succeed I will be able to work with Apache::CVS not via the Apache. I am not sure it is such a good idea, but I will give it a shot since it can short my development process a lot. Any more ideas ? Thanks, shushu In reply to Re: Re: CVS repository via Perl
by shushu
|
|