[petsc-dev] Updating MOAB version during download
Jed Brown
jed at jedbrown.org
Mon Jun 16 13:23:47 CDT 2014
Barry Smith <bsmith at mcs.anl.gov> writes:
> On Jun 16, 2014, at 12:13 PM, Satish Balay <balay at mcs.anl.gov> wrote:
>> and change them to
>> tarball urls for release [which is error prone and fragile]
>
> I agree changing them manually at release is error prone. Hopefully
> it will only be for a very small number of packages.
Just change the logic to prefer the tarball instead of preferring
gitcommit.
> I propose we stop making PETSc snapshots and instead people who
> want to work with the development version can use git. If people
> have machines they want to use petsc-dev on but they don’t have git
> on that machine that is their problem, not ours.
Bitbucket provides tarball downloads of any version (commit, tag, or
branch). People can download those if for some reason they can't use
Git. I don't think we need to hold their hand to do that.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140616/51c009c3/attachment.sig>
More information about the petsc-dev
mailing list