[MacPorts] #50448: Change filenames of binary packages built against libc++ on < 10.9

[MacPorts]

#50448: Change filenames of binary packages built against libc++ on < 10.9
--------------------------+--------------------------------
  Reporter:  mojca        |      Owner:  macports-tickets@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:  2.3.4
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------------------

Comment (by RJVB):

 I have the impression that more and more software assumes C++11 will work,
 and pretty soon that will be true also for later C++ flavours. I think
 that increases the pressure to tackle this issue because motivation to do
 so will only decrease...

 One should probably use a less confusion term than `stdlib`; either talk
 about libstdc++ vs libc++ or about the C++ runtime library.

 Do I understand correctly that you do not suggest changing the default, at
 least for OS versions that do not ship libc++ at all? Is there any
 scenario in which it would be possible (and feasible) to make using libc++
 the default when a system libc++ *is* available?

 > While discussing this it might be worth thinking about potential
 (simultaneous) switch to *.tar.xz for archives which could save quite some
 space both for end users as well as on the buildbots / servers with
 packages.

 This has already been discussed on the ML and/or Trac, but:
 In that case it might be even more beneficial to consider unpacking the
 software images with --hfsCompression, possibly under optional control of
 a setting in macports.conf . Xz'ped archives can be considerably smaller
 than bzip2'ed archives, but HFS compression can reduce the space taken by
 installed ports by quite a bit more.

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