[MacPorts] #28276: arb: Upgrade to 5.2
MacPorts
noreply at macports.org
Sun Feb 13 10:49:38 PST 2011
#28276: arb: Upgrade to 5.2
----------------------------------+-----------------------------------------
Reporter: matt.cottrell@… | Owner: macports-tickets@…
Type: update | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: libpng | Port: arb
----------------------------------+-----------------------------------------
Comment(by ryandesign@…):
* r75953: consolidate configure.env into build.env
Replying to [comment:10 matt.cottrell@…]:
> Allow build_arch x86_64 only. Prompt the user to confirm that
build_arch is set properly in macports.conf. User may have forgotten to
update build_arch after upgrading the OS to a 64-bit version.
I don't think we want that. What if the user's system really is 32-bit
only -- as in, PowerPC G4 or Intel Core (not Core 2)? What if the user is
on Leopard or Tiger, where 32-bit building is the default? If this
software will not work well as 32-bit, you could write a `ui_warn` at pre-
configure time alerting the user to this fact, but I would not prevent the
build if the software will technically work 32-bit. If you like, you can
tailor the message based on whether the user's computer supports 64-bit.
MacPorts uses `sysctl hw.cpu64bit_capable` to determine this; if it prints
"1" the CPU is 64-bit capable; if it shows "0", then it's not. If it's
"1", your message could advise the user to change build_arch; if it's "0",
you could tell the user to buy a new computer. :) In any case, do not
hardcode /opt/local; use ${prefix}.
As I work to commit these individual pieces, evaluating your monolithic
diffs against the original portfile becomes more difficult. For future
proposed changes, please supply a diff against the current port in the
repository making only those changes.
--
Ticket URL: <https://trac.macports.org/ticket/28276#comment:11>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list