One way to do it is to consider the revision control system that you're using part of the solution (instead of maybe part of the problem).

I use CVS. My scripts are not all one kind of program, so they won't all belong in /cgi-bin/ or in ~/bin/ or any other particular location. On my setup there are scripts in all those places and more. Using CVS to do the version control means that the repository where the scripts are stored can be organized, and I try to use categories within the repository tree (subdir names) that relate to what the scripts are for. Then I try to maintain a careful $CVSROOT/CVSROOT/modules file (which is a manual administrative task if you don't employ some kind of 3rd-party system, if one exists).

Using the modules file by doing  cvs co -c allows me to see what the names and locations (in the repository tree) of scripts are, which gives me a pretty good idea of what's in them. If I need to search more, I can use grep on the repository tree. 

-- 
Now, in 2005: The 3 least meaningful terms in online jargon are: 
    troll   flame   rant
These used to actually mean something; but now they've been highjacked by the kind of inferior intellects who, when faced with a more erudite opponent who's employing superior arguments (or simply hanging in there with a disagreeable contention), merely abuse these terms, reducing them just another form of name-calling. ;-)

In reply to Re: Script Organization || not by Intrepid
in thread Script Organization || not by cajun

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.