[Users] release status

Roland Haas rhaas at illinois.edu
Mon Jun 19 12:26:46 CDT 2017

Hello all,

I guess one way to handle this would also be:

* add the LIBS=... workaround to the release notes
* add the code to the master perl detect.pl script after the release as
  a bugfix (which it is)
* wait a week for things to fail catastrophically
* backport to release branch


> On Mon, Jun 19, 2017 at 12:04:44PM -0400, Erik Schnetter wrote:
> >I am viewing this as a work-around -- the user would set LIBS >appropriately in their option list. I am not describing an automated >mechanism here.  
> Doing these things by hand correctly always works. What I want is a workaround for the automation. This ought to work for something central as MPI and something wide-spread as Linux.
> Frank

My email is as private as my paper mail. I therefore support encrypting
and signing email messages. Get my PGP key from http://pgp.mit.edu .
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
Url : http://lists.einsteintoolkit.org/pipermail/users/attachments/20170619/4a0734b4/attachment.bin 

More information about the Users mailing list