petsc-dev directory structure questions

[Satish Balay]

I guess my thoughts in the previous e-mail were all over the place -
so here is an attempt to get something consistant out.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<Barry>

2) putting the ons of sample configure.py files for different systems
into a subdirectory called samples

<Richard>
A much more descriptive name for the 'config' directory would be
something like 'BuildScripts'.

<Lisandro>
* I'm on Richard's side. I believe all the build scripts in 'config'
should be placed in other location, let say 'maint/BuildScripts/'.

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

One issue here is - when you refer to scripts in config - are you
refering to things like just 'linux-gnu.py' or both configure.py &
linux-gnu.py.

** In the current design _both_ scripts are equivalent [wrt user
invocation]. Hence in the same location. **

<option1>
So the current porposal of PETSC_DIR/BuildScripts & PETSC_DIR/config
is _exaclty_ the same organization as what we had before [with
PETSC_DIR/config & PETSC_DIR/python], with dirs being renamed.
PETSC_DIR/python could have aswell be moved to PETSC_DIR/src/foobar
[and it would still be consistant to me].

Issue: Woud user now invoke ./BuildScripts/configure.py?

<option2>
However if the intent is to splitup configure.py & linux-gnu.py, the
organization avaliable is: PETSC_DIR/configure.py, PETSC_DIR/config,
and PETSC_DIR/BuildScripts.

*****
With the above two options , Barrys primary concern with eliminating
one of 'conf' and 'config' is not resolved. [only better renaming is
done, with a cost of different ueser interface with ./configure.py and
./BuildScripts/linux-gnu.py]
******

<option2A>
Now move PETSC_DIR/config to PETSC_DIR/src/config-foobar. This removes
one dir from PETSC_DIR [however BuildScripts & conf, configure.py
still remain]

<options2B>
Also move PETSC_DIR/BuildScripts to PETSC_DIR/maint/BuildScripts.
However with this approach [as we don't distribute 'maint' to users,
this would be loss in usr functionality.

We are attempting all of this reorganization just because the name
'conf' is too close to 'config'. [And I fear we might break more than
what we are fixing]

Satish