Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#37973 closed enhancement (fixed)

RFE: the bzr port should be modified to not use "universal_variant no" if possible

Reported by: cooljeanius (Eric Gallager) Owned by: raimue (Rainer Müller)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: bzr

Description

Replacing the bzr portfile's line that says "universal_variant no" with something like "supported_archs noarch" would be useful, because then it would be possible to have ports with universal variants depend on bzr, without any conflicts in variants.

Change History (5)

comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added; raimue@… removed
Owner: changed from macports-tickets@… to raimue@…

bzr is not noarch; it installs architecture-specific files in ${frameworks_dir}/Python.framework/Versions/2.7/lib/python2.7/site-packages/bzrlib:

$ lipo -info /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/bzrlib/_annotator_pyx.so 
Non-fat file: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/bzrlib/_annotator_pyx.so is architecture: x86_64

If it is possible to do so, it would be great to allow bzr to build universal, of course. Just removing the "universal_variant no" line works for me on Mountain Lion.

comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

bzr's universal variant was disabled in r31638 because the port was using the python25 portgroup and perhaps building python 2.5 software universal was difficult back in 2007, but the port uses python 2.7 now and I don't know of a reason why the universal variant should remain disabled.

comment:3 in reply to:  2 Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to ryandesign@…:

bzr's universal variant was disabled in r31638 because the port was using the python25 portgroup and perhaps building python 2.5 software universal was difficult back in 2007, but the port uses python 2.7 now and I don't know of a reason why the universal variant should remain disabled.

Yeah I had come across that commit when trying to figure out why it was added, but unfortunately the commit message didn't come with that explanation... Anyway, thanks for explaining it to me now though. And also of course just removing the "universal_variant no" line entirely would probably be the best solution; the "noarch" suggestion I made in the OP was just me thinking aloud.

comment:4 Changed 11 years ago by raimue (Rainer Müller)

Resolution: fixed
Status: newclosed

universal_variant no removed in r102989.

comment:5 Changed 11 years ago by cooljeanius (Eric Gallager)

Thanks!

Note: See TracTickets for help on using tickets.