Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
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

Proposal: Always run some scans by default: license, copyright, package, info #398

Open
pombredanne opened this issue Dec 8, 2016 · 2 comments

Comments

@pombredanne
Copy link
Contributor

The default is for now to run license, copyright and package. We need the info to always get a proper inventory of the codebase.

I am also thinking at eventually removing the CLI options to select only certain scans. The rationale is that several scans overlap:

For instance detecting an asserted license in a package manifest is best done by a combo of package detection + minimal license detection on the "license" field for that package. Rerunning license detection on the manifest as if it were a random, unstructured file is not productive nor accurate.

Same for copyrights part of the license text itself (e.g. in a GPL or LGPL for an FSF copyright) or present in a "copyright" field of a package manifest.

@steven-esser
Copy link
Contributor

I think at the very least, we should always default to -i.

I almost always want to use this flag during analysis work, and it is required by a number of our tools (AboutCode manager) and scripts.

I think it would be best to have -i -c and -l as defaults when running scancode without specific flags.

When specific flags are used (scancode -l file.txt output.json for example), scancode should do only what the user tells it. This is handy when running scancode on a specific license text or notice file, for example.

@mjherzog
Copy link
Member

mjherzog commented Feb 8, 2017

Sooner than later we need a way to store a set of options and we could provide an option file called "defaults". It is hard to anticipate all the different ways that people may want to use ScanCode so best to not choose for them, but make is easy for users to set their preferred options.
We can probably merge #209 with this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants