[petsc-dev] related to compiling your source code

[Barry Smith]

> On Apr 14, 2015, at 4:45 PM, Mark Adams <mfadams at lbl.gov> wrote:
> 
> 
> >
> > This has never been a problem.
> 
>    I suspect this is because almost no one knows about PETSC_OPTIONS and uses it.
> 
> 
> This could be a migration path for people using ~/.petscrc ... 

  So people start using PETSC_OPTIONS. They do the same stupid thing of setting something and forget about a year later and then we have to remove PETSC_OPTIONS.  Why do we want to migrate them to something just as dangerous?