[MacPorts] #59888: sparsehash should either be noarch or keep its universal veriant

MacPorts noreply at macports.org
Wed Dec 25 01:27:06 UTC 2019


#59888: sparsehash should either be noarch or keep its universal veriant
-------------------------+--------------------
  Reporter:  devernay    |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  sparsehash  |
-------------------------+--------------------

Old description:

> The following update to the sparsehash port:
> https://github.com/macports/macports-
> ports/commit/79bcaad0315c9229ee841064701ab8b9fbff47ed
> removes the +universal variant, but doesn't set noarch, thus preventing
> dependent ports (eg py27-shiboken) to build a +universal variant
>
> The fix is simply to leave the +universal variant, reverting the above
> commit. I think it's not a big deal to have a +universal port which is
> really noarch, and actually identical to the non-universal one.

New description:

 The following update to the sparsehash port:
 [79bcaad0315c9229ee841064701ab8b9fbff47ed/macports-ports]
 removes the +universal variant, but doesn't set noarch, thus preventing
 dependent ports (eg py27-shiboken) to build a +universal variant

 The fix is simply to leave the +universal variant, reverting the above
 commit. I think it's not a big deal to have a +universal port which is
 really noarch, and actually identical to the non-universal one.

--

Comment (by ryandesign):

 Hm. You may be right.

-- 
Ticket URL: <https://trac.macports.org/ticket/59888#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list