On Tue, 23 Dec 2014, Barry Smith wrote: > > > On Dec 23, 2014, at 7:08 PM, Jed Brown <[email protected]> wrote: > > > > Barry Smith <[email protected]> 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 :-).
Will the matlab stuff ever get packaged - unless we change to octave? [in which case we might have to follow octave packaging guidelines..] Satish > > > > $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? > > Barry > > > > > > > > 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. > >
