Hi Paul, thanks for the reply.... On Sun, Aug 4, 2013 at 10:10 AM, Paul LeoNerd <leon...@leonerd.org.uk> wrote: > On Sun, 7 Jul 2013 17:08:46 -0400 > Chris Marshall <devel.chm...@gmail.com> wrote: > >> The only alternative is to do the actual install >> process to see if it "just works" or to drill down >> into the implementation to determine how the >> module does its work and thence to deduce if >> it supports windows (64bit) for example. > > Er, I missed the text on the first mail ;) > > The approach I take with Alien modules is to bundle the upstream > tarball in the dist, and build/install it directly into perl's archlib > directory: > > https://metacpan.org/release/Alien-libtermkey > https://metacpan.org/release/Alien-unibilium
For windows platforms which have no supported package manager, the only option is to either bundle the needed code or a web site to get the source or binaries. I notice that the Alien::libtermkey and Alien::unibilium appear to be unix-ish only. There were no PASSes reported for either mswin32 or cygwin platforms. It appears that since the two libraries appear to be unix-only, maybe there is no way to support windows platforms (I'm not sure why cygwin didn't work). If so, that is exactly the critical information needed so windows users don't go down a dead end trying to use those modules or perl modules requiring them. I haven't come up with a good way to do that for the general case. If one knows a priori any such restrictions, at least the docs should indicate that and the Makefile.PL or Build.PL could return NA in testing. Maybe it would be useful to carve out OS specific packages under the Alien:: moniker. What about Alien::Unix::libtermkey ? Cheers, Chris > -- > Paul "LeoNerd" Evans > > leon...@leonerd.org.uk > ICQ# 4135350 | Registered Linux# 179460 > http://www.leonerd.org.uk/
