Re^4: Appending $VERSION to package name in Makefile.PL

Thanks.

The target layout is pretty clear by now, and I even know what I'd have to do when doing it "by hand".

What I'm trying to do now is to coax MakeMaker into doing it for me (bonus points if it does a "stage install" by default, so as not to thrash the "hot" installation).

Regards

Comment on Re^4: Appending $VERSION to package name in Makefile.PL

Replies are listed 'Best First'.
Re^5: Appending $VERSION to package name in Makefile.PL by Anonymous Monk on Apr 19, 2012 at 12:50 UTC
If you're referring to Appending $VERSION to package name in Makefile.PL or Re^2: Appending $VERSION to package name in Makefile.PL, that is the wrong thing to do	[reply]
Re^6: Appending $VERSION to package name in Makefile.PL by oldtomas (Novice) on Apr 20, 2012 at 06:34 UTC
Hi. I'm sorry I don't understand. By that is the wrong thing to do you mean: "coaxing Makefile.PL to do the library install to a different lib is the wrong thing to do?" If yes: could you elaborate? If no: what is the wrong thing to do? Thanks	[reply]
Re^7: Appending $VERSION to package name in Makefile.PL by Anonymous Monk on Apr 20, 2012 at 06:53 UTC
Like I hinted in Re^3: Appending $VERSION to package name in Makefile.PL , do not install your module, don't overwrite existing installs, don't rename the module name Renaming the module is the wrong solution (whether from Makefile.PL or otherwise). If you want to rename something, rename the directory where the module gets installed. Telling Makefile.PL to install the module in a custom directory is one option. Simply not installing the module at all (not running Makefile.PL) is another option. Distributing a binary ( a complete perl ) is another option I provided several links (and links to links), if you're interested how each solution works, you should follow them You can also see an overview of the different variations of these solutions at the slideshow linked at Seen in PerlWeekly newsletter: Carton CPAN dependency manager	[reply]