[petsc-dev] elemental in nightly builds with g++-4.6

[Satish Balay]

On Wed, 9 Oct 2013, Jed Brown wrote:

> Jack Poulson <poulson at stanford.edu> writes:
> 
> > That makes sense, though I'm surprised that PETSc is switching between
> > the development branch and the last release (0.81) on the fly.
> 
> We use Git if it's available and fall back otherwise.  I should have
> made a tarball for the git commit because we're advertising 64-bit int
> support.  My intent is that branch 'jed/elemental-int64' will not be
> merged to 'master' until it is upgraded to Elemental 0.82.  But people
> that want to run 'next' can use it in the mean time.

When we add git URLs - we should update the tarball URLs to equivalent
git snapshots.  The intent for the multiple url support in package.py
is to be able to get the same source via multiple paths.

So perhaps the tarball URL should be: https://github.com/elemental/Elemental/archive/master.tar.gz

[or the url automatically crated from self.giturls + self.gitcommit . note: bitbucket appears to use 'get' instead of 'archive']

But switching from elemental-dev to elemental-release should be a different matter.
[both git & tarball urls should probably changed simultaneously]

Presumably we won't have fallback tarballs for git repos on ftp.mcs

Satish