Ok, so far we have prefix/conf prefix/lib/conf (or petscconf or petsc) prefix/etc/conf (or petscconf or petsc) prefix/share/conf (or petscconf or petsc
Barry On Tue, 12 Jun 2007, Lisandro Dalcin wrote: > Barry, > > What about putting 'conf' inside '$PETSC_ARCH/lib' > > In the build directory, arch specific 'conf' dir will be in > > $PESC_DIR/$PETSC_ARCH/lib/conf > > In the install directory, it will be > > '$PETSC_PREFIX/lib/conf' > > In such a case, perhaps you can use 'petsc' instead of 'conf'. I am > taking here python as example, in my box I have under '/usr/lib' > > /usr/lib/libpython2.4.so -> libpython2.4.so.1.0 > /usr/lib/libpython2.4.so.1.0 > /usr/lib/python2.4 > > And also I have under '/usr/include' > > /usr/include/python2.4 > > This is great because the standard 'include' dir is not populated with > many headers, but for petsc this would complicate things. > > > > On 6/11/07, Barry Smith <bsmith at mcs.anl.gov> wrote: > > Good point. etc was also suggested. Adding the petsc is > > kind of ugly with the non-installed version, for example > > petsc-dev/$PETSC_ARCH/shared/petsc/petscrules > > instead of > > petsc-dev/$PETSC_ARCH/shared/petscrules > > These things are still up in the air and will be adjusted > > as good ideas come in. > > > > Barry > > > > On Mon, 11 Jun 2007, Lisandro Dalcin wrote: > > > > > If one of the goals of the new build system is to be more symmetric > > > with the GNU model, in order to make life easier for packagers, so I > > > think the '$PETSC_PREFIX/conf' location should be renamed, perhaps to > > > '$PETSC_PREFIX/share/petsc'. I believe 'conf' is not a 'standard' > > > location. > > > > > > > > > > > > > > > > > > >