Universal Binaries

[timlee at rochester.rr.com]

If I hand edit the /opt/local/share/macports/Tcl/port1.0/portmain.tcl file, will it be 'merged' automatically the next time macports version is bumped or is it a simple 'rm' and then 'cp' the new file in?

thanks

---- Harry van der Wolf <hvdwolf at gmail.com> wrote: 
> 2009/1/25 Joshua Root <jmr at macports.org>
> 
> > Timothy Lee wrote:
> > > Ryan-
> > > Thanks for the tip on not adding the '/' to the --prefix - that fixed
> > > the problem.
> > >
> > > In regards to the +universal variants - my universal_target only
> > > contains "i386" as suggested by Josh. My other settings look like this:
> > >
> > > *# Options for Universal Binaries (+universal variant)*
> > > *
> > > *
> > > *# MACOSX_DEPLOYMENT_TARGET*
> > > *universal_target        10.4*
> > > *
> > > *
> > > *# the SDK "sysroot" to use *
> > > *universal_sysroot       /Xcode3_0/SDKs/MacOSX10.4u.sdk*
> > > *
> > > *
> > > *# machine architectures*
> > > *universal_archs         i386*
> > >
> > > Again- my variants.conf only contains +universal and my macports.conf as
> > > the variants_conf path set correctly - yet I still see the deployment is
> > > being set to 10.5.
> >
> > Argh, sorry, I forgot - this is broken in the released version. I fixed
> > it here: <http://trac.macports.org/changeset/44363>
> >
> > You can apply that change to
> > /opt/local/share/macports/Tcl/port1.0/portmain.tcl, or install MP from
> > svn trunk if you're so inclined.
> >
> 
> That might also be the reason why it worked for me "by accident". I
> installed the "pre 1.7 svn trunk" somewhere in October/November and worked
> with it until 5th or 6th of January. I skipped the official 1.7 version and
> installed a new version of the svn trunk (somewhere on 4-6 January),
> obviously including the patch (didn't even know there was one).
> Sorry for also introducing some confusion due to this.
> 
> Harry