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

[Jed Brown]

Satish Balay <balay at mcs.anl.gov> writes:

> in this case the url would be https://github.com/elemental/Elemental/archive/89e7ddc52db68dc5a3f2635733293d7349dbd518.tar.gz

Will we have to name it to match elemental* ?

>> Those fallback tarballs are currently a maintenance issue.  Can we automate it?
>
> Hm - currently updating the url in package.py is a manual process. so
> updating ftp.mcs would be done at the same time.
>
> But if we want some kind of automatic fallback for all urls - perhaps we
> can setup a squid-proxy cache at mcs - and configure always uses that?
> [maybe it won't work for all cases..]

Yeah, something like that could work.  It would be enough to cache
things under either the SHA1 or the "upstream" URL.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20131009/3ac3fdbf/attachment.sig>