On Thu, 8 Aug 2013 07:00:07 -0400 Chris Marshall <devel.chm...@gmail.com> wrote:
> To the original proposal, I've added the > following thoughts: > > - make test in Alien::XXX should be > FAIL if it was not possible to either > detect/configure an existing XXX or > to install a new copy. (This is > different than the perl level stuff but > it seems to do the right thing here) > > - Have the build process give information > on why things didn't work: e.g., no GNU > make, libtool, tty/ptty, ... This is much > more useful than "OS doesn't work" of > any flavor. This /is/ what NA with the "OS unsupported - MESSAGE" does. Again; observe that with the two Alien modules I mentioned, they give NA with a message about being unable to find GNU libtool. It's not possible to easily turn this into a FAIL, because FAIL would have to mean that it did at least configure successfully, and then failed at the testing stage. At this point there isn't an easy way to notate why. > - If a failure occurs, provide information > on how to "do it yourself" even if only > a short paragraph and a link. "unable to find GNU libtool" - surely suggests to the user that they should install GNU libtool then try again? I could add that paragraph of text if you think it would be useful. -- Paul "LeoNerd" Evans leon...@leonerd.org.uk ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/
