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]
> 
> True. I actually realized that as I was hitting send

For now I've changed name to '%version-%arch'.

Perhaps we should provide a configure option --with-module-name=foobar
[for situations where the user can provide a prefered name]

> > BTW: Is the following notation ok? [google didn't help]
> > 
> > prepend-path PATH /home/balay/spetsc/asterix64/bin:/home/balay/spetsc/bin
> 
> It seems to work, but 

For now - I've pushed the above notation.

Satish

Reply via email to