On 2 March 2018 at 15:02, Ryan Schmidt wrote: > On Mar 1, 2018, at 16:09, Mojca Miklavec wrote: > >> Yes. I still find it super painful that we did not manage to migrate >> to libc++ over all those years due to a basically "trivial" issue. >> >> My suggestion would be to use one hacking session during the meeting >> to implement a few lines of code that take care of renaming the >> binaries + test whether users could switch to libc++ using migration >> tool written by Umesh. > > Please also take a look at this related issue about having separate libc++ > and libstdc++ portindexes, and what name to use to differentiate them: > > https://trac.macports.org/ticket/55471 > > It doesn't have to use the same naming scheme as the archives we distribute, > but it could, so it could relate.
I wrote some comments to that ticket. Mojca
