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

What does "RM" mean in the output? #46

Closed
steveklabnik opened this issue Aug 4, 2017 · 5 comments · Fixed by #51
Closed

What does "RM" mean in the output? #46

steveklabnik opened this issue Aug 4, 2017 · 5 comments · Fixed by #51

Comments

@steveklabnik
Copy link

Name                                   Project Ver     SemVer Compat  Latest Ver
aho-corasick->memchr                      0.1.11            RM            RM

Might be nice to have this explained somewhere.

@Frederick888
Copy link
Collaborator

Yeah, improving the documents would be a must. Some help messages are needed to be updated as well.

As far I could see, the new 0.4.0 release works slightly different in terms of:

  1. Packages that are removed after an update are marked as RM
  2. --depth 0 literally means checking only the root now (note that there was a related issue just got fixed Inconsistent output caused by --root parameter #47)

@Frederick888
Copy link
Collaborator

And by the way, is the provided example an actual output? Coz I just had a glance at aho-corasick and found that memchr was still in its dependency list.

@steveklabnik
Copy link
Author

This is actual output, yeah. I forget what project I used it on.... gah!

@Frederick888
Copy link
Collaborator

@steveklabnik I'm working on #51 and RM has been replaced by Removed. Apparently it turned out that saving several characters was completely unnecessary and even confusing. 😅

This label is what you get when a dependency is removed from the dependency tree after an update.

@casey
Copy link

casey commented Sep 10, 2017

I was a little confused by Removed. I think Superfluous or Unnecessary might be more precise.

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 a pull request may close this issue.

3 participants