On Thu, 19 Dec 2013 22:19:59 +0000 Paul "LeoNerd" Evans <leon...@leonerd.org.uk> wrote:
> Instead I have two choices: > > * Forcibly install Alien::libtermkey /anyway/ by listing it under > configure_requires, before I had any chance to ask pkg-config if > such was in fact necessary. This feels wasteful. > > * Have Alien::libtermkey's Build.PL check using pkg-config whether > the library is already installed; and if so do no real work other > than to provide a lightweight wrapper around that. Actually a third idea comes to mind: * Subclass Module::Build, so that I can perform a regular dynamic 'requires' on Alien::libtermkey if it turns out I need to. The subclassing then exists in order to delay needing to know the compiler/linker arguments until actual ./Build time. By now, it can rely on having Alien::libtermkey installed if required, so can ask it for arguments. They all feel equally messy and non-ideal in some way or other though. :( Advice? -- Paul "LeoNerd" Evans leon...@leonerd.org.uk ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/
signature.asc
Description: PGP signature
