On May 17, 2012, at 7:25 p.m., Bjarne D Mathiesen wrote: >> Your idea won't work right. If the path to an arbitrary perl is >> inserted into any of the files installed by the port, the build is no >> longer repeatable. > > But I'm *not* inserting an arbitrary value of Perl into any file. > At configure the variable will be evaluated and turned into a hard value > as far as I can tell.
The build would not be repeatable because it would depend on factors external to the given port -- namely, it would be dependent on whatever perl5 points to at the time you build. (Also, if you don't have perl5 installed at all, it will default to perl5.12 and install it if it's missing, even if you have perl5.14.) > As far as I can see, my proposal is no different from what's already > working in *all* p5- ports. Try eg : > less $(port file p5-acme-lolcat) p5-acme-lolcat defines subports, each of which depends on a specific version of Perl. Having subports is not the same as doing a build with whatever Perl happens to be lying around. vq _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
