[petsc-dev] related to compiling your source code

[Barry Smith]

> On Apr 14, 2015, at 4:30 PM, Mark Adams <mfadams at lbl.gov> wrote:
> 
> 
> 
> How about when they copy their .bashrc file - which might include
> PETSC_OPTIONS env variable?  [or LD_LIBRARY_PATH to wrong version of
> libraries]
> 
> 
> This has never been a problem.

   I suspect this is because almost no one knows about PETSC_OPTIONS and uses it.


>  Perhaps everyone know about .bashrc and must deal with it, but .petscrc falls of the radar and they/we forget about it ...
>  
> Is the current thought to remove PETSC_OPTIONS env variable aswell?
> 
> Perhaps ~/.petscrc things can go into .bashrc somehow?
>  
> 
> How about PWD/.petscrc and PWD/petscrc? remove them aswell?
> 
> These are the "normal" rc files that are really used to augment the command line.  And in the case of FORTRAN codes, which don't add an arg parser of some sort, it is the command line.
> 
> Mark 
>  
> 
> Satish
> 
>