-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
--extract should not be an option but a separate command #52
Labels
Milestone
Comments
I strongly agree. There are so many possible twists and turns for extraction so that it needs to be part of a scanning pipeline, but not deeply embedded in another step in the scanning pipeline. |
pombredanne
added a commit
to pombredanne/scancode-toolkit
that referenced
this issue
Aug 10, 2015
pombredanne
added a commit
to pombredanne/scancode-toolkit
that referenced
this issue
Aug 10, 2015
…ption for aboutcode-org#52 * --extract is now in the extractcode command for aboutcode-org#52 * refactored the command code to sperate progress reporting from actual scan.
This is fixed now |
pombredanne
added a commit
that referenced
this issue
Nov 24, 2015
pombredanne
added a commit
that referenced
this issue
Nov 24, 2015
* --extract is now in the extractcode command for #52 * refactored the command code to sperate progress reporting from actual scan.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Extraction feels like a wart in the scancode command. It does not share any of the semantics of the command and should be best as a separate command such as
extractcode
that would only extract things.The text was updated successfully, but these errors were encountered: