* Paul "LeoNerd" Evans <leon...@leonerd.org.uk> [2014-01-09 20:30]:
> I'm not following.
>
> Alien::libtermkey does indeed configure_require Alien::unibilium.
>
> When the perl-level Alien::libtermkey's Build.PL runs, it is of course
> free to make queries of Alien::unibilium. But what good does this do?
Well, so you have a pkg-config (et al) question, not an Aliens question.
> Alien::libtermkey's next action is to unpack the bundled
> libtermkey.tar.gz and run "make install" on it. A:l cannot communicate
> anything it has learned from A:u into this Makefile, because
> libtermkey's Makefile tries to enquire directly of pkg-config itself.
What he said:
* David Mertens <dcmertens.p...@gmail.com> [2014-01-09 22:20]:
> Your build system can set environment variables that pkg-config
> listens to, and then when Module::Build calls system('make'), those
> changes to environment variables will carry through. […]
Furthermore, you can pass flags to the Makefile or any other of the
commands you `system`, depending on what they accept.
> Furthermore, there is no reason you can't patch the build files after
> unpacking them. Is this brittle? Absolutely!
If you do have to resort to this, it doesn’t even have to be brittle: if
you are shipping a tarball of the alien or downloading a particular of
it version during *.PL, you know exactly what’s in the tarball, so you
know exactly what your patch code will do.
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
