[MacPorts] #28276: arb: Upgrade to 5.2

[MacPorts]

#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@…):

 Replying to [comment:13 matt.cottrell@…]:
 > Sorry, what portfile keyword returns "1" or "0" based on the 64-bit
 capability of the hardware?  I searched the portfiles for "sysctl
 hw.cpu64bit_capable" and I can't find any examples of portfiles using that
 syntax.

 No port keyword does that, but the `sysctl` Tcl procedure (which is a
 wrapper around the `sysctl` shell command) does. gtk2, gtk3 and gprolog
 are the ports I found that are using this, and MacPorts base does as well.

 Be aware that `sysctl hw.cpu64bit_capable` was introduced with Leopard; it
 will generate an error message on Tiger.

 {{{
     if {${os.platform} == "darwin" && ${os.major} >= 9} {
         if {[sysctl hw.cpu64bit_capable] == 1} {
             ui_msg "64-bit capable"
         } else {
             ui_msg "not 64-bit capable"
         }
     } else {
         ui_msg "unable to determine 64-bit capability"
     }
 }}}

 On Tiger, if build_arch is a 32-bit arch, just assume 64-bit capability is
 not available; support for 64-bit building was spotty on Tiger anyway.

 Replying to [comment:14 matt.cottrell@…]:
 > That's right, arb_tcp.dat is a config file that will be edited by the
 user.  We need to preserve its contents and not overwrite it when the port
 is upgraded.  Likewise the files pts and macros should not be overwritten
 upon upgrading the port.

 pts and macros are directories, not files. The pts directory is empty as
 installed, so nothing need be done there. The macros directory contains
 some files. Is the user going to be modifying those, or just adding their
 own files in the directory? If the latter, nothing need be done; MacPorts
 will not overwrite or remove files it doesn't know about.

-- 
Ticket URL: <https://trac.macports.org/ticket/28276#comment:15>
MacPorts <http://www.macports.org/>
Ports system for Mac OS