Sounds like a pretty good idea to me, however i have to wonder: why both tar and gzip? It seems to me that your goal is just to get all the information (files, manifest, etc) packed into a single file, and tar works fine on its own. gzip will give you smaller files at the tradeoff of the time it takes to uncompress (and recompress?) them. So unless size is a major concern (probably not when dealing with perl source code), i see it as unnecessary.
You could also consider that there's no requirement for your files to end in '.tar' if you're using them solely for the purpose of acting as plugins for your program. if you give them a more distinctive extension (.ppi for perl plug-in?) it will take some of the guesswork out of figuring out which files are plugins and which are garbage in any given directory.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||