petsc-dev directory structure questions

[Lisandro Dalcin]

* 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.


On 12/14/07, Richard Tran Mills <rmills at ornl.gov> wrote:
> A much more descriptive name for the 'config' directory would be something
> like 'BuildScripts'.  'config' doesn't hold any real configuration info; just
> scripts for doing the configuration.  Seems like the name should somehow
> reflect this.  Just my 0.5 cents.
>
> --Richard
>
> Barry Smith wrote:
> >
> > On Dec 13, 2007, at 5:07 PM, Satish Balay wrote:
> >
> >>
> >> For one, I think conf/configure.py should be ./configure.py
> >
> >    How come this wasn't done originally or hasn't been changed to
> > this already?
> >
> >>
> >>
> >> And conf and config are 2 different things - so they should be in
> >> separate locations. merging them doesn't make sense to me. The primary
> >> issue I see is the names "conf" and "config" are extremely close to
> >> each other.
> >
> >    Exactly, so how the heck is anyone suppose to know what is in either
> > one of them?
> >
> >>
> >>
> >> One option is to move config to src/config [this would work well with
> >> ./configure.py]
> >
> >    config stuff is not source code so cannot go in there.
> >
> >>
> >>
> >> Satish
>
>


-- 
Lisandro Dalcín
---------------
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594