On Tue, Dec 3, 2013 at 8:44 PM, SiegeLord <[email protected]> wrote: > I don't think any of these options are ideal. I don't want to suggest > solutions to these issues because I'm not sure how things are supposed to be > used/what the planned design is. Does anybody use rustpkg seriously today? > Is everybody making workspaces with a github.com/<user> directory where they > develop their software?
I usually (i.e. in other languages I work with) develop dependencies "in-line" as they were cloned by the package manager, at least if they need deep integration with the surrounding project and can not be easily tested/developed in isolation. It's not such a horrible situation as long as the package manager is smart enough to avoid wiping your stuff on its own. That said, a pretty good option I think is to have a command like npm link [1] that would allow you to tell rustpkg to set up a symlink to another dir on the disk, yet without interfering/polluting the project's source itself. [1] https://npmjs.org/doc/cli/npm-link.html Cheers -- Jordi Boggiano @seldaek - http://nelm.io/jordi _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
