Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rustpkg: Make rustpkg commands work without a package ID #7419

Closed
wants to merge 1 commit into from

Conversation

catamorphism
Copy link
Contributor

r? @brson rustpkg build, if executed in a package source directory inside
a workspace, will now build that package. By "inside a workspace"
I mean that the parent directory has to be called src, and rustpkg
will create a build directory in .. if there isn't already one.

Same goes for rustpkg install and rustpkg clean.

For the time being, rustpkg build (etc.) will still error out if
you run it inside a directory whose parent isn't called src.
I'm not sure whether or not it's desirable to have it do something
in a non-workspace directory.

@emberian
Copy link
Member

emberian commented Jul 7, 2013

@catamorphism
Copy link
Contributor Author

@cmr Yeah, I'm working on it.

@catamorphism
Copy link
Contributor Author

I'll re-push after #7681 lands.

`rustpkg build`, if executed in a package source directory inside
a workspace, will now build that package. By "inside a workspace"
I mean that the parent directory has to be called `src`, and rustpkg
will create a `build` directory in .. if there isn't already one.

Same goes for `rustpkg install` and `rustpkg clean`.

For the time being, `rustpkg build` (etc.) will still error out if
you run it inside a directory whose parent isn't called `src`.
I'm not sure whether or not it's desirable to have it do something
in a non-workspace directory.
@catamorphism
Copy link
Contributor Author

r? @graydon -- This was approved before, but I've changed a fair amount.

bors added a commit that referenced this pull request Jul 20, 2013
r? @brson `rustpkg build`, if executed in a package source directory inside
a workspace, will now build that package. By "inside a workspace"
I mean that the parent directory has to be called `src`, and rustpkg
will create a `build` directory in .. if there isn't already one.

Same goes for `rustpkg install` and `rustpkg clean`.

For the time being, `rustpkg build` (etc.) will still error out if
you run it inside a directory whose parent isn't called `src`.
I'm not sure whether or not it's desirable to have it do something
in a non-workspace directory.
@bors bors closed this Jul 20, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Feb 10, 2023
wildcard_enum_match_arm lint takes the enum origin into account

fixes rust-lang#7419

---

changelog: Enhancement: [`wildcard_enum_match_arm`]: Now lints missing private variants, for local enums
[rust-lang#10250](rust-lang/rust-clippy#10250)
<!-- changelog_checked -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants