On Thu, Aug 29, 2002 at 06:47:26AM -0700, drieux wrote:
>
> ah! I see! you really are in the
>
> have code, the rest is temporary data files
I'm not sure I catch your drift here. Did a line get dropped from the
email?
>
> 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>
>
No to both questions! Which means I need to include both. I have just
added some switches for this script. I guess I can just add a switch
for --help.
#i'v already defined my switch --help and attatched it to $help
if ($help){
print "in order to use this script..."
}
As far as perldoc goes, if I include any pod in the script, then
typing perldoc rtf2xml should output the documentation? (I'll try this
out right now. I'll probably have the answer before you respond!)
> 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...
>
Thanks. This is all useful info. Right now in order to run the script,
a user needs:
1. the code
2. the character_set file
3. a folder called rtf2xml_dir located in /usr/share
4. a temp folder located in the above folder.
It is pretty easy to write a script to make a folder and copy the
character_set file to this folder. Will all users have permission to
make such a folder?
And where should I put the executable script? In /bin, or /usr/bin, or
what?
I think I'll go with simply writing my own simple script for making
the installation. I'll also give explicit instructions in README on
how to install the few components by hand, (if the user wants to) as
well as how to change the place the script writes its temporary files,
and where it reads its data. (I put a variable called $directory at
the beginning of the script so a user can change it easily if he
wants.)
I guess I need to work on the pod documentation. I believe I should be
able to simply follow the Perl Cookbook.
Thanks
Paul
>
>
>
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
************************
*Paul Tremblay *
*[EMAIL PROTECTED]*
************************
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
