On Aug 9, 2010, at 9:07 AM, Alexander Hansen wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 8/9/10 6:01 AM, Daniel E. Macks wrote:
>> Many dozens of perl5.10.0 variants of perlmodule packages don't build
>> on 10.6/i386 (i.e., the 32-bit side of the "universal" system-perl)
>> because they all clone the same CompileScript for Build.PL that does
>> not pass the single-arch tricks. I'm fixing them because they're
>> broken. I have contacted many of theirs' maintainers several times
>> over the past few weeks, but it's all still broken. I'm sick of not
>> being able to use half of the perl world on the one platform that we
>> tend to say is best supported.
>> 
>> We really need an intrinsic support for this...a huge swath of CPAN
>> uses Module::Build, so fink should support it cleanly just like we do
>> with MakeMaker (Makefile.PL). The goal is an explicit trigger for
>> alternate default CompileScript and InstallScript for Type:perl.
>> Which of these new .info fields do y'all like?
>> 
>> 1. PerlType: that takes values of "makemaker" or "module::build", that
>> defaults to "Makefile.PL".
>> 
>> 2. DefaultScript: that takes values of "autotools" "makemaker"
>> "module::build"? Bonus: extensible to any other new build systems we
>> feel like supporting, and lets packages get the type:perl magic even
>> if they use autotools (or vice versa).
>> 
>> 3. Automatically detect presence of Build.PL and switch to that mode
>> insead of MakeMaker.PL. Bad: some distros include both, so wouldn't
>> allow maintainer to choose which one works best without going back to
>> hardcoding everything. This was proposed years ago on tracker.
>> 
>> 4. [insert your idea here]
>> 
>> dan
>> 
> 
> 2) sounds pretty good to me.  Having more options "under the hood" means
> fewer maintainer tricks, which may fail on upgrade, to get things to build.

I agree, 2 sounds like the best idea as it offers more flexibility.

Daniel


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to