petsc-dev directory structure questions

[Satish Balay]

Any mail with 'config' in the begining of a line is interpreted by
majordomo as 'admin' commands. Such mails are getting blocked. I'm
reformatting the text and resending this e-mail to see if it will
work.

Satish


---------- Forwarded message ----------
Date: Fri, 14 Dec 2007 10:24:04 -0500
From: Richard Tran Mills <rmills at ornl.gov>
Subject: Re: petsc-dev directory structure questions
In-reply-to: <e7ba66e40712140652h64537474hffc7fb89ff74b0a5 at mail.gmail.com>
To: petsc-dev at mcs.anl.gov
Reply-To: rmills at ornl.gov

  Isn't everything currently in the 'config' directory a build script of some 
  sort?  There are two sorts of scripts: example $PETSC_ARCH.py scripts and then 
  the general-purpose stuff like configure.py and the stuff in the config/PETSc 
  directory.  But broadly speaking (though perhaps it's a bit of a stretch for 
  config/PETSc) this stuff is all scripts for builds.  So why not just change 
  the name of 'config' to something more descriptive?

--Richard

Lisandro Dalcin wrote:
> * I'm on Richard's side. I believe all the build scripts in 'config'
> should be placed in other location, let say 'maint/BuildScripts/'.
> 
> * I'm also on Barry's side. Code for configuration should not go
> inside 'src/'. All this should go inside 'config/'
> 
> * And Satish suggestion make a lot of sense. Perhaps the
> 'configure.py' could even be renamed to 'configure', but perhaps this
> can cause trouble in some OS's.
> 
> The problem with 'conf' being similar to 'config' remains.