Satish Balay <[email protected]> writes: > On Mon, 16 Jun 2014, Barry Smith wrote: > >> >> This email thread is way to complicated for me. Is the final decision >> >> 1) If a git and .tar.gz are BOTH given for a —download then they should >> represent the same thing? > > The defaults in package.py should match. Right now > --download-package=URL can take .tar.gz stuff - but not a git URL [as > far as I can remember] > >> >> Sounds reasonable. (But why have both, just incase a website is down?) >> How do we make sure they always match? They will get out of synch! > > I think the thought was [Jed, Matt should correct me] - if the user > has 'git' installed - then configure should prefer downloading 'git' > url. [else .tar.gz url]
When Git is used, the user can query the exact version and (not yet implemented) we could have automatic updates. That versioning is harder with tarballs, though we could (and probably should) track the hash of the tarball so that we know when to upgrade.
pgpFM5gV2vIs6.pgp
Description: PGP signature
