On 2014/04/07 22:00, Andrew Fresh wrote: > My annoyance is that they picked a different set of compatibility > options than got picked in perl.port.mk which means I need to provide my > own do-install for this port and another that now uses > Module::Build::Tiny. > > http://www.openbsd.org/cgi-bin/cvsweb/ports/infrastructure/mk/perl.port.mk?rev=1.23 > > Apparently Module::Build allows the flags to have, or not have prefixed > double dashes and accepts an equal sign after the flag. It also lets > you put ${FAKE_TARGET} after these flags. > > Module::Build::Tiny doesn't do that, it requires ${FAKE_TARGET} to be > first, then flags with double dashes after and doesn't understand the =. > > Plus, it doesn't remember from the configure phase what the flags were > so I have to specify them for the do-install phase. > > do-install: > @cd ${WRKSRC} && perl \ > ${MODPERL_BUILD} ${FAKE_TARGET} \ > --destdir "${PREFIX}" \ > --install_path lib="libdata/perl5/site_perl" \ > --install_path libdoc="man/man3p" > > Is this what I get for any ports that use Module::Build::Tiny?
Hmm... Do we need a CONFIGURE_STYLE=modbuildtiny? Or do Module::Build::Tiny's requirements also work with Module::Build, in which case we could just modify things for CONFIGURE_STYLE=modbuild?
