[email protected] writes: > On Jan 20, 2014, at 12:49 PM, Sean Farley <[email protected]> > wrote: > >> >> [email protected] writes: >> >>> Barry Smith <[email protected]> writes: >>>> Where should we put the files that end up in conf? Should we >>>> simply not install those? >>> >>> I don't think we should install logs. If it were up to me, I would put >>> the makefiles in $prefix/share/petsc/, but I would install a script >>> petsc-config that can be used to dump the configuration as well as >>> provide configuration (a la pkg-config). I think we should recommend >>> that users use this petsc-config script instead of including makefiles. >>> >>> What do you think? >> >> Jed's suggestions here would be great for package maintainers. As an >> added bonus, it'd be great if $prefix/share/petsc-$foo could be be >> configurable (so that multiple installations could be live >> side-by-side). > > This would allow multiple copies of the “share” stuff but if the library > is in $prefix/lib/libpetsc.dylib how can multiple installations exist side > by side?
There would have to a configurable subprefix, e.g. include/petsc-3.4, lib/petsc-3.4, etc. Though, it's not as big a deal to me.
