On Tuesday, December 4, 1956, at 07:56 , Paul Tremblay wrote:
[..]
> Okay, I'm getting closer to finishing the d**n beast of a script, so I
> need to think about how to distribute it. This script will be a
> command line utility. Right now it has no switches:
>
> rtf2xml <file>
>
> I want to make it easy to use for people who don't know perl. Should I
> still use a module?
[..]
ah! I see! you really are in the
have code, the rest is temporary data files
sorry for not quite catching your drift the first time.
just a dumb-bunny question - but if I type
rtf2xml --help
will your code dump me some 'advice'? and/or
perldoc rtf2xml
show me if
rtf2xml <input_file> <output_file>
would work - or that in this release it is only
sending output to STDOUT?
that being the other rack of basics - all you
really need to do to distribute it would be
to hang the code on a webPage and let folks 'save to file'
from their browser....
The next level of complexity is to either go with
the Make::Maker approach of building an installer
based upon the usual
perl *.PL
make install
model - or you will want to look at the other
option of
a) hand crafting an installation script
b) adopting someone else's "package installer"
- rpm/pkgadd
and complying with their standard.
The basic stuff that you will want to put into the
general release are
a) README - what we are about
- clues to any other documentation
b) ChangeLog - when we did what to this for why
c) The Installation Stuff
- how to check for all the dependencies
- how to check for the installer's desires and wishes
as well as explain to them if they try to install into
places they shouldn't
- how to actually install it...
d) The Code Stuff
- the one item - at this point
e) Manifest - what should be in the tarball
This way the person who just wants 'the application' Can
"just install it" - without having to understand what all
the rest of that stuff is about - while others will be able
to keep track of how this evolves as it evolves...
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
