Hsiao, Chang-Ping wrote:
CVS is easy to use but confusing at first.
This could be the root of my reservations.
Indeed, I don't get what I'm saying either.Once you get used to it, you should not complain. I don't quite get your saying "I don't however feel that the organizational logic of a websites code base fits well into the CVS paradigm." Isn't your files hierarchical? If so, why is CVS not fitting your purpose?
My organisation is something like (slightly over-simplified),
_lib/Example/Control/section_a.pm
_lib/Example/Control/section_b.pm
_lib/Example/Control/section_c.pm
_lib/Example/Config/section_a.pm
_lib/Example/Config/section_b.pm
_lib/Example/Config/section_c.pm
_lib/Example/Model/section_c.pm
_lib/Example/Model/section_c.pm
_lib/Example/Model/section_c.pm
_tmpl/section_a/view1.html
_tmpl/section_a/view2.html
_tmpl/section_a/view3.html
_tmpl/section_b/view1.html
_tmpl/section_b/view2.html
_tmpl/section_b/view3.html
_tmpl/section_c/view1.html
_tmpl/section_c/view2.html
_tmpl/section_c/view3.html
I though CVS was more suited for something which looks more like
_lib/Example/Section_a/Control
_lib/Example/Section_a/Model
_lib/Example/Section_a/View/1
_lib/Example/Section_a/View/2
_lib/Example/Section_a/View/3
etc....
i.e. more suited to a "procedural" orangisation than an "object" organisation
Then again, like i said... perhaps my assumptions were too short sighted.
Ric.