Why doesn't this project use Module::Build?
Parse and decode METAR, TAF, SYNOP, BUOY, AMDAR and write data as XML
Brought to you by:
metaf2xml
Menu
▾
▴
the install script for metaf2xml is very complex, but the problem it solves has already been solved by Module::Build, and before that by ExtUtils::MakeMaker.
Using Module::Build would not only greatly reduce the amount of code currently devoted to installation, it would also provide a well-tested cross-platform packaging and installation solution, make the software much easier to submit to CPAN, and make it much easier to incorporate into other packaging systems (e.g. FreeBSD's ports, or homebrew for MacOS X)
Hi,
you are right, Module::Build looks a good choice for an installer. I didn't like ExtUtils::MakeMaker for its dependency on make. I would have ignored M::B even if I had seen it, because the description says "Build and install Perl modules". The Perl modules from the project are an important part but I think without the scripts and XSL stuff they are much less useful. If you have experience with M::B I'd be happy if you could give a few hints how to provide the same features as install.pl. I'm hesitant to add a new dependency but happy to do it if it saves effort for me and/or improves the usability for others.
I thought about publishing at CPAN. But I think the program is so limited in use that it wouldn't be useful to a lot of people, and maintaining it there wouldn't be worth the additional effort.
Kind regards,
Thomas