[petsc-dev] elemental stuff still broken

[Karl Rupp]

Hey,

>> When he updates, we should be making a one-line commit in
>> config/PETSc/packages/elemental.py to use his new version.
>
>     How do we know that “we should be making a one-line commit in elemental.py”? And who should make the “one line commit”?
>
>     Anything that relies on “should” is not a good system,

Ideally it is Jack who pushes the one-line change whenever he publishes 
a new release. Maybe he's also willing to run a separate branch on 
GitHub (i.e. something like PETSc's maint) which we can use in 
master/next. Our maint would need a stable release version, though...

However, I'm not sure whether this is worth the additional maintenance 
troubles. With some branch tracking it becomes harder for *us* to 
determine which elemental version was used in a build if user problems 
show up.

Best regards,
Karli