On Fri, 25 Jan 2013, Blaise A Bourdin wrote: > the usual naming scheme is just the version number, but for petsc, most > supercomputing centers use %version-%arch > the installer will copy the file into $MODULEPATH/petsc/%version-%arch, or > the user to $HOME/.modulefiles > > Of course, %version-%arch is a really silly name out of context. How about > petsc-%version-%arch, somewhere within $PETSC_DIR/$PETSC_ARCH, or > $PETSC_DIR/$PETSC_ARCH/modulefiles/%version-%arch ?
And PETSC_ARCH has no singificance with prefix install [the significant text is in the prefix-path - and one doesn't have to match PETSC_ARCH to this significant text] BTW: Is the following notation ok? [google didn't help] prepend-path PATH /home/balay/spetsc/asterix64/bin:/home/balay/spetsc/bin I have some fixes [except for the modfile name] which I can push. thanks, Satish > > Blaise > > > On Jan 24, 2013, at 6:19 PM, Satish Balay <balay at mcs.anl.gov> > wrote: > > > On Thu, 24 Jan 2013, Matthew Knepley wrote: > > > >> On Thu, Jan 24, 2013 at 3:42 PM, Blaise A Bourdin <bourdin at lsu.edu> > >> wrote: > >> > >>> I am attaching a very basic module file for reference. One would need to > >>> update petsc_dir and petsc_arch upon deploying these, or perhaps configure > >>> can do it. > >>> > >>> I actually use this to easily switch between builds and debug / optimized > >>> versions > >>> > >> > >> Pushed something that writes your simple module file to > >> lib/modules/PETSc.mod. It would now be good to get feedback > >> to make this the right thing. > > > > The name conflists with f90 modules. Perhaps there is a different > > notation for software modules? > > > > Also for prefix install we should set PETSC_ARCH="" > > > > And for inplace install - do we also add PETSC_DIR/bin to PATH? > > > > Satish > > > >
