[petsc-dev] no module named cmakegen

Matthew Knepley knepley at gmail.com
Mon Aug 23 17:26:47 CDT 2010


On Mon, Aug 23, 2010 at 10:21 PM, Satish Balay <balay at mcs.anl.gov> wrote:

> On Mon, 23 Aug 2010, Satish Balay wrote:
>
> > Now that there are more and more standalone scripts - perhaps we need
> > a better consistant way to handle this - but I don't know what that
> > is..
>
> mercurial way is to have 'hg' be the frontend script to all commands.
> i.e no invocation of individual scripts ..
>
> Perhaps we should adopt that?


That requires a Mercurial 'install', which is not different than a) or c)
namely

  c) Put PETSC_DIR in your PATH, which is env var manipulation

  a) Change /usr/bin, which is always in the path (like installing inside
Python)

   Matt


>
> Satish
>
-- 
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100823/58299f5d/attachment.html>


More information about the petsc-dev mailing list