2 ms·

This will certainly make our lives easier. BUT. 1) Why store a package, wouldn't an index rather than another repository be more efficient and flexible. Carg

by demarq 12y ago

This will certainly make our lives easier. BUT. 1) Why store a package, wouldn't an index rather than another repository be more efficient and flexible. Cargo already has the capability to get packages from git urls... I had some other nicks but I see this is on github so I'll try and contribute there. I like the site, and can't wait to test it out. Thanks to all who have been working hard on this!

mercurial 12y ago
> 1) Why store a package, wouldn't an index rather than another repository be more efficient and flexible. I suppose the authors experienced the "guy deleted his Github repo" effect one time too many. It's a very sensible decision. Getting packages for git urls is fine when you're hacking something together, but there is absolutely no way I'd put anything in production relying on something that fragile.
- demarq 12y ago
  I think it's even worse depending on a repo whose author refuses to or is unwilling to maintain. Besides git is hardly fragile especially if we are talking github. I happily clone and pull projects all the time without a single hitch. Also if you think about it github/attlassian are all dedicated to task with datacenters around the globe, while for the rust team the repo might be somewhat of a side gig.
  - mercurial 12y ago
    I'm not so worried about Github going down as I am about people removing their repos. And why do you think depending on a repo is worse than depending on Github? If the package is not maintained anymore, license willing, you can always fork it and bump the dependencies yourself, even if, in the worst of cases, you need to keep the fork local. However, if it turns out you have to maintain a lot of third-party libraries yourself, it's a sign either of a bad ecosystem, or that you picked the wrong libraries.
    - demarq 12y ago
      I guess at the end of the day so long as cargo has the git option people like me will always get our code fresh from the source, with the maintainers consent. It's not like I'm being forced to use the crates-repo. Let's agree on one thing we shouldn't be maintaining other peoples abandoned/illegal libs, however thanks to them being posted on the crates-repo permanently, we'll continuously keep running into them...
      - mercurial 12y ago
        > Let's agree on one thing we shouldn't be maintaining other peoples abandoned/illegal libs, however thanks to them being posted on the crates-repo permanently, we'll continuously keep running into them... Maybe. But at least, if you pick your or somebody else's unmaintained code from five years ago, you have a fighting chance of making it compile and run.

by demarq 12y ago

mercurial 12y ago

> 1) Why store a package, wouldn't an index rather than another repository be more efficient and flexible. I suppose the authors experienced the "guy deleted his Github repo" effect one time too many. It's a very sensible decision. Getting packages for git urls is fine when you're hacking something together, but there is absolutely no way I'd put anything in production relying on something that fragile.

demarq 12y ago
I think it's even worse depending on a repo whose author refuses to or is unwilling to maintain. Besides git is hardly fragile especially if we are talking github. I happily clone and pull projects all the time without a single hitch. Also if you think about it github/attlassian are all dedicated to task with datacenters around the globe, while for the rust team the repo might be somewhat of a side gig.
- mercurial 12y ago
  I'm not so worried about Github going down as I am about people removing their repos. And why do you think depending on a repo is worse than depending on Github? If the package is not maintained anymore, license willing, you can always fork it and bump the dependencies yourself, even if, in the worst of cases, you need to keep the fork local. However, if it turns out you have to maintain a lot of third-party libraries yourself, it's a sign either of a bad ecosystem, or that you picked the wrong libraries.
  - demarq 12y ago
    I guess at the end of the day so long as cargo has the git option people like me will always get our code fresh from the source, with the maintainers consent. It's not like I'm being forced to use the crates-repo. Let's agree on one thing we shouldn't be maintaining other peoples abandoned/illegal libs, however thanks to them being posted on the crates-repo permanently, we'll continuously keep running into them...
    - mercurial 12y ago
      > Let's agree on one thing we shouldn't be maintaining other peoples abandoned/illegal libs, however thanks to them being posted on the crates-repo permanently, we'll continuously keep running into them... Maybe. But at least, if you pick your or somebody else's unmaintained code from five years ago, you have a fighting chance of making it compile and run.