This becomes fun after a few years, especially if you're deciding to CVS your repository.. (it is a little harder to re-arrange directories in CVS.. although isn't impossible).
Personally I create a base ~/bin directory for storing my scripts.. why in bin? I can't really explain other than it's just evolved into a method that kinda works for me. Under that directory I have:
/bin/script/perl
/bin/script/bash
and then under that I have my scripts, each in a subdirectory.
There have been situations where I've written several scripts that are associated, in which case I start collecting them into their own subdirectory. E.g. I might have something like:
/bin/script/perl/address
.../chrstr
.../cisco
.../cisco/2600
.../cisco/3500
.../graphit
.../icecream
.../mechanize
.../mechanize/autotrader
.../mechanize/banking
.../mechanize/webmail
.../photoconvert
.../test
I guess the best advice I can have is sit down and have a crack at your own method of organisation. Then after a year or so, review it! Good luck!
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.