merge for universal builds (was: Re: [31954] trunk/base/src/port1.0/portutil.tcl)

Ryan Schmidt ryandesign at macports.org
Thu Dec 13 18:18:52 PST 2007


On Dec 12, 2007, at 18:29, Markus Weissmann wrote:

> On Dec 13, 2007, at 12:23 AM, Ryan Schmidt wrote:
>
>> On Dec 12, 2007, at 11:50, mww at macports.org wrote:
>>
>>> Revision: 31954
>>>          http://trac.macosforge.org/projects/macports/changeset/ 
>>> 31954
>>> Author:   mww at macports.org
>>> Date:     2007-12-12 09:50:49 -0800 (Wed, 12 Dec 2007)
>>>
>>> Log Message:
>>> -----------
>>> add 'merge' function for mergin multiple (single arch) destroots  
>>> into one (universal) destroot
>>
>> How does this compare with
>>
>> http://trac.macports.org/projects/macports/browser/users/pipping/ 
>> merge.rb
>>
>> and how does it relate to backup() and lipo() in
>>
>> http://trac.macports.org/projects/macports/browser/trunk/base/src/ 
>> port1.0/portutil.tcl
>>
>> ?
>
> would you mind being a bit more specific?

Does your merge() function serve the same purpose as Elias's merge.rb  
script? I mean, I'm happy to see something like this in MacPorts  
base, implemented in tcl, as opposed to ruby.

backup() and lipo() were other functions that were added at some  
point to assist in creating universal versions of ports that don't  
build universal all at once. Does your merge() function obsolete these?

Granted we need more universal support in base, but we should  
coordinate things amongst ourselves, not duplicate effort, and not  
create different ways of doing the same thing.



More information about the macports-dev mailing list