Re: [Module::Build] perl Makefile.PL INSTALL_BASE=~
On Fri, Nov 19, 2004 at 05:26:14PM -0500, Michael G Schwern wrote: http://rt.cpan.org/NoAuth/Bug.html?id=8528 Folks want Module::Build and MakeMaker to install files into the same place. This is a perfectly legit concern. The problem comes when you use perl Makefile.PL PREFIX=~. MB has no equivalent and its Makefile.PL wrapper does not honor PREFIX. This is because the PREFIX algorithm is mad on the best of days, broken on the worst and you really don't want to have to support two implementations of it. One idea is to make MakeMaker's prefixification code callable by MB. This would let MB emulate PREFIX without having to duplicate the code. However, this will require some work on a part of MM that I prefer to just leave alone. A simpler, and faster to implement, alternative is to go the other way around. Have MakeMaker emulate MB's install_base functionality. Its also saner and less prone to bugs than PREFIX. Most of the time people just want a solution to How do I install modules without being root. install_base does a better job of that than PREFIX. Me too. Executables to bin, perl modules to lib/perl or similar. I don't really care about whether a module is architecture specific or what have you. I want to be able to set $PATH and $PERL5LIB to something obvious and have my libs just work. I don't really care what the mechanism is as long as it is obvious and documented. What I don't want is to have to root around under $PREFIX to try to figure out how to set $PERL5LIB to get all the necessary libraries included, or to have to set 10 different settings during the build process to make it go. Ignorance should be bliss, really. :-) Austin
Re: perl Makefile.PL INSTALL_BASE=~
On Nov 19, 2004, at 4:26 PM, Michael G Schwern wrote: A simpler, and faster to implement, alternative is to go the other way around. Have MakeMaker emulate MB's install_base functionality. Its also saner and less prone to bugs than PREFIX. That's not a bad idea. Sounds good to me. (Not bad == good). -Ken
META.yml, MakeMaker and the license field
-BEGIN PGP SIGNED MESSAGE- Moin, I already wondered many times why the license for most of my modules is not set/shown at search.cpan.org, even though modules like BigInt have simple the perl license (being part of the core etc). Seems like setting a license: perl line in META.yml would fix this. However, everytime I run make dist, the META.yml file is overwritten again, with the license line missing. And it seems that MakeMaker doesn't have a LICENSE = setting. Of course, I can set NO_META to true, and modify the META.yml file manually, but that looses the handy property that META.yml is autogenerated with the correct dependencies etc. (e.g. everytime I change Makefile.PL, I have to remember to change META.yml, which I surely will forget from time to time. Ugh.) So, is it possible to have MakeMaker to generate the license line automagically, or I am something missing? Best wishes, Tels - -- Signed on Sat Nov 20 13:05:45 2004 with key 0x93B84C15. Visit my photo gallery at http://bloodgate.com/photos/ PGP key on http://bloodgate.com/tels.asc or per email. When it's done in 2001. - 2000 Christmas card about Duke Nukem Forever (http://tinyurl.com/6m8nh) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQZ8zlncLPEOTuEwVAQHi2Qf/USuERWZpS1+HemdjrVn4aHhqHKHwsRLS D5lc8KNgHZwQydErP9iY2FFQ1VV7whsc5FNzf0eDiGEgcb4m5EL8678gfKY8qKZ9 WBRAgTPI4g1ccMz+wiz7hIOGtsZY/7eKUVHFPzmj8Kglt7zQDy00tq6lz1bGgiMa ZgDft9Ofh471S1XJsgcWm7rOGkU6ixHA0r0rGSE1zXA//HYMTng7NDEIO/EVzHD1 dOMtw3fGOfIUs+vBoRnDG2n6DBEU7psCU4NQvSomJJiRegYKLz8MIdVg9kWPXl7U hqxJsNLIaIY8B6nLWaXrzdhUf4DJLDfho6m8MofIWY1LVli2c4SpFQ== =OV5A -END PGP SIGNATURE-
Re: META.yml, MakeMaker and the license field
Tels wrote: I already wondered many times why the license for most of my modules is not set/shown at search.cpan.org, even though modules like BigInt have simple the perl license (being part of the core etc). Seems like setting a license: perl line in META.yml would fix this. However, everytime I run make dist, the META.yml file is overwritten again, with the license line missing. And it seems that MakeMaker doesn't have a LICENSE = setting. Of course, I can set NO_META to true, and modify the META.yml file manually, but that looses the handy property that META.yml is autogenerated with the correct dependencies etc. (e.g. everytime I change Makefile.PL, I have to remember to change META.yml, which I surely will forget from time to time. Ugh.) So, is it possible to have MakeMaker to generate the license line automagically, or I am something missing? Current versions of MM don't have an option for setting the license. I think I sent a patch a while back for the next release. You can find an example of how you can override MM's rule for creating META.yml in: http://search.cpan.org/src/MHX/Convert-Binary-C-0.56/Makefile.PL Search for 'sub MY::metafile' Randy. PS: If you do override the generation of the meta file, it's a good idea to follow Marcus' convention for setting 'generated_by' = 'Your::Module::Name Makefile.PL'. Or if you create it by hand (NO_META), then set 'generated_by' = 'Author Name, by hand'. These conventions make it easy to see who's doing what with META.yml.
