Ryan Schmidt wrote: > > On May 17, 2012, at 17:30, Bjarne D Mathiesen wrote: > >> 1) We still need a policy decision as to whether is should be hardcoded >> as now -or- we'll use my proposal that I consider more fully >> developed regarding future releases of Perl > > I thought Joshua already explained why your proposal cannot work. >
There's this one : http://lists.macosforge.org/pipermail/macports-dev/2012-May/019285.html > 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. 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) And Joshua never answered my question for clarification. -- Bjarne D Mathiesen København N ; Danmark ; Europa ---------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit miljø MacOS X 10.7.3 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev