On Thu, Jun 12, 2014 at 2:57 PM, Arno Hautala wrote: > On Thu, Jun 12, 2014 at 3:08 AM, Mojca Miklavec wrote: >> >> Ideally it would check if the os already provides 1.9 and use that >> one if it does, else depend on whatever ruby is already installed >> by MP. > > Isn't that the type of non-reproduceable build that MacPorts tries to avoid?
It could be "if using 10.9 or later, don't depend on external ruby". For the rest ... many packages use +python27, +python33, ... or +gcc47, +gcc48, ... So the port could provide +ruby19, +ruby20, +ruby21 and then the installation would rewrite all the ruby scripts in the software to use exactly the intended ruby version from hardcoded location. The port could check whether any of those rubies is already installed on the system and use the most appropriate variant. Or simply use +ruby21 and let the user pick a different one. Mojca _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
