[petsc-dev] Sean is going to love this

Barry Smith bsmith at mcs.anl.gov
Tue Dec 23 20:26:27 CST 2014

> On Dec 23, 2014, at 7:08 PM, Jed Brown <jed at jedbrown.org> wrote:
> Barry Smith <bsmith at mcs.anl.gov> writes:
>>  Sure, but they have to go into a "legal" location. Where would that
>>  legal location be? We'd start by putting the data as is in the legal
>>  location, then add a bin/petsc-config to process that data (crudely)
>>  then refine both the storage of the data and the bin/petsc-config
>>  over time.
> $libdir/petsc/ if we want to be like libtool and pkgconfig.

  lib - Currently we put Matlab compiled stuff here (Matlab uses arch specific suffixes so versions for any architecture can be dumped in this same place, of course the PETSc library in the upper directory is specific :-).
> $sysconfdir/petsc/ if we think of these as host-specific.

  etc - This is silly.
> $datadir/petsc/ if we think of them as host-independent (similar to man
> pages).

  share -   Some of our external packages put stuff here.

  I think of share as something that kind of works for any architecture (like manual pages) and not things that a specific to a particular architecture. Since conf stuff is particular to an architecture does this mean we should put conf there? And for backwards compatibility have  a link from $prefix/conf for a while?


> By default:
>  libdir = $prefix/lib/
>  sysconfdir = $prefix/etc/
>  datadir = $prefix/share/
> I think we could use any of these without getting in trouble with
> package managers.

More information about the petsc-dev mailing list