[MacPorts] #55471: Use separate portindexes for libc++ on older systems

[MacPorts]

#55471: Use separate portindexes for libc++ on older systems
--------------------------+-----------------
  Reporter:  ryandesign   |      Owner:
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+-----------------

Comment (by ryandesign):

 Replying to [comment:2 mojca]:
 > I would keep the default names at their current values and would change
 the one for `libcxx` (even though: doesn't `libc++` work as folder name?)

 It would. But elsewhere in MacPorts, we have adopted the convention that
 "+" becomes "x" so I adopted it here. We did that in port names so that
 the "+" would not be confused with the syntax for specifying a variant;
 that reason doesn't apply here. I also wasn't sure if PortIndex files
 would ever be transferred over http; if so, the "+" would need to be
 percent-encoded to "%20", and I wasn't sure if that might introduce
 problems.

 > according to your proposal, except that I don't know if it makes any
 sense whatsoever to do `libc++` on PPC.

 As far as I know, at this time, libc++ doesn't work on PowerPC generally.
 I think Ken had found a way to make it work with some additional hacking.

 > It would potentially make sense to support gcc's libstdc++v3 on PPC and
 that one could be called
 > {{{
 > PortIndex_darwin_9_libstdcxx_powerpc
 > }}}
 > where `libstdcxx` would stand for libstdc++v3. I don't know if we have
 any explicit support for that in base though.

 I don't know; I hadn't heard of that before.

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