[65087] trunk/base/src/macports1.0/macports.tcl

Ryan Schmidt ryandesign at macports.org
Sat Apr 3 00:36:39 PDT 2010


On Apr 3, 2010, at 02:17, Jeremy Huddleston wrote:

> the proto packages have no arch, so they're marked:
> 
> universal_variant no
> 
> xorg-server depends on these protos.  I want to install it +universal, and base aborts because it can't satisfy the proto dependencies as +universal.
> 
> Do noarch ports need to be updated again in a way other than 'universal_variant no'?  If so, how should we do that?  I searched macports-dev and came up empty.  grepping dports for "noarch" showed nothing useful either.  Looking at your 
> patch, it looks like we have to force the build arch to "noarch" in these packages.  Is that right?  Are we going to have to revbump all these packages (X11 protos, data files, perl and python scripts, etc) for this?

As jmr said, we have no way to indicate a port is noarch in MacPorts 1.8.x. "universal_variant no" was a poor substitute.

Now that we can use "supported_archs noarch" in trunk, hopefully MacPorts 1.9+ will realize this means there's no reason to add a universal variant, and "universal_variant no" won't be manually necessary anymore. (Does trunk already do this?)





More information about the macports-dev mailing list