Yeah, I misunderstood, apologies. I was reading over the documents you linked earlier to see if there was any further information on how versions were going to be handled. Surely forcing packages without version control to be 0.1 is restrictive? I feel as though the central metadata thing should still be optional, i.e. you can supply a version number in the case that you will be distributing the project as a tarball. It seems pkg.rs will be kept as an optional tool for custom compilation logic, so it makes sense that the metadata could be optional as well.
On Fri, Jun 28, 2013 at 1:30 PM, Graydon Hoare <[email protected]> wrote: > On 13-06-27 07:55 PM, SiegeLord wrote: > > Well, consider this. Let's say I have a project A has a different >> project B as its dependency, which I, by accident of history, host on >> github. >> >> I.e. project A has this line in it (I think this is the proposed syntax): >> >> extern mod "github.com/SiegeLord/ProjectB**"; >> >> How would I get rustpkg to use my local copy of it? >> > > You would make a local directory > "$W/github.com/SiegeLord/**ProjectB<http://github.com/SiegeLord/ProjectB>" > in some workspace $W that's part of your RUST_PATH, that contains your > local override. > > > I assume it will try >> to do: rustpkg install github.com/SiegeLord/ProjectB which will only >> work the way I want if I re-create that directory structure on my system. >> > > Correct. I think Zack misunderstood your objection. To override a pkgid > locally you would need to create a local directory of the same name. > > -Graydon > > > ______________________________**_________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/**listinfo/rust-dev<https://mail.mozilla.org/listinfo/rust-dev> >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
