Repository navigation
Allow package IDs to refer to the middle of a source repository #6408
Description
Sub-bug of #5677
Currently, rustpkg assumes that a remote package ID refers to the root level of a particular source repository. @brson suggested that to obviate the need for servo to use git submodules, we could allow package IDs to point into a subdirectory of a repo. It's unclear whether we should implement this. See discussion at https://etherpad.mozilla.org/Rustpkg-Servo-meeting
Activity
emberian commentedon Jul 23, 2013
This seems like a good idea to me. Imagine a C library that ships rust bindings in a 'rust' subdirectory.
lilyball commentedon Aug 23, 2013
Go allows you to reference a sub-path of a repo. It checks out the correct repo, and only builds that sub-path.
lilyball commentedon Aug 23, 2013
If this is implemented (and I think it should be), then rustpkg should also stop recursively searching for
lib.rs(and the other magic files) and instead require them to be in the root. This is because rustpkg assumes that the last path component of the pkgid is the name of the library, and it would be very confusing if I could type bothrustpkg install github.com/foo/barandrustpkg install github.com/foo/bar/bazand have both build the same library, but only the latter successfully install.rustpkg: Support sub-package-IDs
auto merge of #9146 : catamorphism/rust/rustpkg-sub-package-ids, r=br…
Auto merge of rust-lang#6408 - pro-grammer1:master, r=oli-obk