As I understand it, Alien packs the module for you, or otherwise "does
what it takes". Having only done a quick basic reading of the Alien
docs, it seems that it's a brute force thing for when you REALLY want
the lib and you have only CPAN.pm with which to get it. (Although it
might shortcut in the appropriate cases)
I'd hoped for something much more simple and declarative. Something
where we (Perl) don't actually do anything, but provide enough hints for
others to be able to make it the appropriate cross-language dependencies
of their own in each environment.
So needs_lib entries result in a debian module using libfoo on Debian,
or on RPM, or etc...
Adam K
A. Pagaltzis wrote:
* Adam Kennedy <[EMAIL PROTECTED]> [2006-01-28 09:00]:
If a Perl module needs libfoo then it should be stated in the
metadata somewhere so that the binary packaging system can
resolve that generalised dependency into the appropriate action
for that environment.
++
How does Alien:: stack up here in your opinion?
Regards,
