Re: [MacPorts] #33649: cgal update 3.9 -> 4.0

#33649: cgal update 3.9 -> 4.0
--------------------------------+-------------------------------------------
 Reporter:  mmoll@…             |       Owner:  vince@…          
     Type:  update              |      Status:  new              
 Priority:  Normal              |   Milestone:                    
Component:  ports               |     Version:                    
 Keywords:  haspatch            |        Port:  cgal              
--------------------------------+-------------------------------------------

Comment(by sean.michael.farley@…):

 Replying to [comment:18 raphael@…]:
 > I think the best way to test new/updated ports is to put the Portfile
 into the current directory and the patches into {{{./files}}} and to use
 {{{port <action>}}} without any portname. Or just use a
 [http://guide.macports.org/chunked/development.local-repositories.html
 local Portfile repository].

 Yes, I usually do this but after building cgal a few times, I wanted a <
 10 min way to see if the rpath was built correctly.

 > By the way, the
 [/browser/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl cmake
 portgroup] already has a debug variant. Do we really need to override this
 variant?

 I would love to have a global variant definition that would maintain debug
 symbols but nothing seems to preserve the debug symbols kept in .dSYM
 except for running dsymutil manually (before the .o's are deleted)
 {{{
 eval exec dsymutil [glob ${destroot}${prefix}/lib/*.dylib]
 }}}

 Maybe the above could test for the existence of .dylib's then run the
 command, and that could be sent as another patch to
 [/browser/trunk/dports/_resources/port1.0/group/cmake-1.0.tcl cmake
 portgroup]?

--
Ticket URL: <https://trac.macports.org/ticket/33649#comment:19>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
_______________________________________________
macports-tickets mailing list
macports-tickets@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-tickets