Re: LLVM 7.1.0: how to proceed?

2019-02-26 Thread Dimitry Andric
On 6 Feb 2019, at 19:58, Brooks Davis  wrote:
> LLVM 7.1.0 will be release shortly and contains a single
> fix which breaks the LLVM Libra ABI in order to fix an
> incompatibility with GCC 8.2.  A bug describing the issue is at
> https://bugs.llvm.org/show_bug.cgi?id=39427.
> 
> My current plan is:
> - Copy devel/llvm70 to devel/llvm71 and update.
> - Perform a coordinated switch of all dependencies, to llvm71 (e.g. do an
>   exp-run with the switch made and llvm70 removed).  All ports with
>   library dependencies would get PORT_REVISION bumps.
> - DEPRECATE llvm70 and set a short expiration.
> 
> Does this sound like a reasonable plan?

If you were going to drop llvm70 anyway, why not just keep the port and
only bump the 'internal' version number?  Or do you want to reduce
possible confusion which might be caused by the "70" suffix no longer
corresponding to the actual libllvm.so version number?

That said, your approach seems fine to me.

-Dimitry



signature.asc
Description: Message signed with OpenPGP


LLVM 7.1.0: how to proceed?

2019-02-06 Thread Brooks Davis
LLVM 7.1.0 will be release shortly and contains a single
fix which breaks the LLVM Libra ABI in order to fix an
incompatibility with GCC 8.2.  A bug describing the issue is at
https://bugs.llvm.org/show_bug.cgi?id=39427.

My current plan is:
 - Copy devel/llvm70 to devel/llvm71 and update.
 - Perform a coordinated switch of all dependencies, to llvm71 (e.g. do an
   exp-run with the switch made and llvm70 removed).  All ports with
   library dependencies would get PORT_REVISION bumps.
 - DEPRECATE llvm70 and set a short expiration.

Does this sound like a reasonable plan?

-- Brooks


signature.asc
Description: PGP signature