Jo Walsh wrote:
i want to make an RDF::Simple package that will eventually have both
Serialiser.pm and Parser.pm in it, but i'm not sure how to make a package for more than one module - so a user can 'install RDF::Simple' and get
everything in it, including some utility modules. 'perldoc perlnewmod'
isn't really helping me out much here.
There are several ways to do it, but what I do (and I believe it's more or less what most do) is to have a lib/ subdirectory in my distro in which I put the hierarchy of my module and update the MANIFEST to match. So you'd have:
RDF-Simple/ lib/RDF/Simple.pm lib/RDF/Simple/Parser.pm ...
(provided it's RDF::Simple::Parser and not RDF::Parser, in which case change accordingly).
IIRC make ci updates your MANIFEST for you but I tend to update it by hand because I usually have lots of stuff I don't want to be automatically put in there, and it'd be too much work to add them to the skipped files.
the little serialiser is TT based; if i need to stick a TT template somewhere on the filesystem in a default INCLUDE_PATH, how would i do that as part of the regular module install process, and where might be the best place to put it?
I guess INCLUDE_PATH is a TT thing so I don't know much about that. What make install does is copy INST_* to the matching INSTALL*. Maybe you just need the SCRIPT (INST_SCRIPT and INSTALLSCRIPT) variants. There are also ugly tricks to manipulate the Makefile before it gets written if you need more power. All of this is in ExtUtils::MakeMaker.
As a side question: are there nice tricks to write XML using TT in an error-free fashion? I'd be curious to look into them, new ways of writing XML being always of interest since it's such a painful task.
-- Robin Berjon <[EMAIL PROTECTED]> Research Engineer, Expway http://expway.fr/ 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
