Re: MakeMaker for testing only

As Courage says, you can dispense with the libscan sub. In your release kit, you need to distinguish between the following uses of a .pm module:

Modules that must be there for your module to work. These are pre-requisites, and should be listed (with minimum version numbers if required) in PREREQ_PM, but not included in the kit.
Additional modules that work alongside the main .pm you are delivering, and you want to be installed with the module. Place these in an appropriate subdirectory of the lib directory (you may need to create a lib directory).
For example, if we have a module My::Foo, which is the main module, but we also want to distribute My::Bar, you need the following paths
```
Foo.pm
lib/My/Bar.pm
[download]
```
Modules only needed for testing or installation, that are 'thrown away'. Put these in the top level directory as all tests are run with this as current working directory.

Hope this helps

rinceWind

By the way, for a glimpse of the future, you might like to look at Module::Build, which Schwern and others are pushing for new modules, and I believe is going into the 5.10 core.

Comment on Re: MakeMaker for testing only Download Code

Replies are listed 'Best First'.
Re^2: MakeMaker for testing only by tall_man (Parson) on Apr 16, 2003 at 14:27 UTC
I don't understand how I could dispense with the libscan sub. If I placed scripts, modules, cc files, and so on in the top-level directory (or in any subdirectory for that matter), won't they all be scanned by MakeMaker and get copied into blib when I do a make? I tried echoing out the file names that are passed to my fake libscan, and all the .cc, .h, *.pm files are included. Before I filtered out the ones I didn't want, they appeared in the sections C_FILES, H_FILES, PM_TO_BLIB, etc. of my Makefile. As I mentioned, this is a C++ main program with embedded perl, so I am not trying to install it like a perl module. I have my own installation scripts already. But perhaps there are ways to adapt the MakeMaker installation process to my needs. I'll look into it further.	[reply]

Replies are listed 'Best First'.

Re^2: MakeMaker for testing only
by tall_man (Parson) on Apr 16, 2003 at 14:27 UTC

I tried echoing out the file names that are passed to my fake libscan, and all the *.cc, *.h, *.pm files are included. Before I filtered out the ones I didn't want, they appeared in the sections C_FILES, H_FILES, PM_TO_BLIB, etc. of my Makefile.

As I mentioned, this is a C++ main program with embedded perl, so I am not trying to install it like a perl module. I have my own installation scripts already. But perhaps there are ways to adapt the MakeMaker installation process to my needs. I'll look into it further.

[reply]