Re: Module and external files

I would pick a combination of #2 and #3. Include the latest files with the distribution, but remind the user that newer files may be available and where to get them (and warnings about compatibility). They should be separate from your module so that it's easy for the user to update them. (Unless your module is extremely tightly coupled to the contents of these files, then I'd just include them in the module and be done with it)

duff

Comment on Re: Module and external files

Replies are listed 'Best First'.
Re^2: Module and external files by Miguel (Friar) on Oct 18, 2004 at 15:32 UTC
"Unless your module is extremely tightly coupled to the contents of these files" It is indeed. These files are the sources of information. Without them the module doesn't work at all. Without these files the module is useless.	[reply]
Re^3: Module and external files by Fletch (Bishop) on Oct 18, 2004 at 15:42 UTC
You could use PAR to package everything into a single file and then distribute that. You'd then use `PAR::par_handle( $0 )` to get access to the contents of your extra files.	[reply] [d/l]