You say that subversion/cvs seems bit too much. But then you go on to enumerate a wishlist that sounds almost exactly like the list of features of a good version control system.

My advice is to install either CVS or subversion, and build on top of that. If you'd rather keep control of the project, you need not give CVS wite priviliges to other people - you can keep it to yourself, or give it to people who have earned your trust through consistent quality contributions.

Come to think of it, you're going to need some sort of version control system for your own use anyway, so making it available to others is just spreading goodness.

In reply to Re: Patching/Updating Perl scripts by matija
in thread Patching/Updating Perl scripts by Ace128

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.