I looked into other version control systems a while back. For an open source project it seemed to come down to rcs, sccs, cvs and subversion. Since subversion was then unreleased, cvs was a clear choice. Subversion's promises sounded really good though.

It is due to my lack of knowledge and the inflexibility of cvs that I asked my questions in the first place. The idea is not to find the one and only one valid way but to understand the trade-offs involved in the various alternatives.

For instance moving all target, intermediate and scratch directories up out of the CVS tree simplifies versioning. But would that create a bad first impression by over flowing its expected namespace when folk create a workspace? I suspect so.

I restructured my project not long ago. Having learned a bit the hard way I am looking at doing it again now. I'd like to learn a bit the medium way.

Now I have hundreds of files. When I have lots more will it still be as easy to restructure my repository? Should I not be concerned to plan ahead?

Did I misunderstand the docs? .cvsignore files only effect the user's workspace, not everyones view of the repository.

I don't find your responses too satisfying -- they seem to reflect an offhand attitude to the subject. I realize this could come from vast experience and great knowledge of version control systems but your posts don't impart enough to me to know this.

Thank you again for your kindness in trying to help.

In reply to (Re:)+ CVS Directory Structure by rir
in thread CVS Directory Structure by rir

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.