Yea thats right It's just a prototype. It's designed to work cross platform but not built for it yet.
The final product would probably use git since it would enable all the semver queries to be run locally and reduce payloads when updating regularly. Along with the dev time benefits that Tony mentioned. It also wouldn't rely on git tags fully it would support commits and branches. Together I think git calls these things refs and treats them pretty similarly so it's easy to support all of them > On Dec 21 2015, at 6:32 pm, Stefan Karpinski <[email protected]> wrote: > > I think it's meant as a prototype. Most prototypes only work on the platform they were developed on initially. Not using git for transport simplifies some things but complicates others. > > > > On Mon, Dec 21, 2015 at 12:10 AM, Tony Kelman <[[email protected]](mailto:[email protected])> wrote: > >> Correct me if I'm wrong, but you appear to be downloading package source as tarballs rather than git clones, which defeats the purpose of Julia packages being active git repositories where you can easily branch, make changes, and submit pr's from them. And change versions with just a checkout (and maybe fetch first). And you're relying on git tags existing within the package repository, which is a best practice but not strictly enforced for current metadata tags. This also distinctly does not look like it was designed to work cross platform. > >
