-
Notifications
You must be signed in to change notification settings - Fork 24
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
Classify cdx component type file #141
base: main
Are you sure you want to change the base?
Conversation
Below is a quick test using
All good so far.
In the above example, I think the following would be clearly classified incorrectly:
Not sure which is worse: that we just classify everything as |
Signed-off-by: Henri Rosten <[email protected]>
584988e
to
693e1cc
Compare
Using wget as an example target, and the changes from this PR@693e1cc:
|
@arianvp: Any thoughts? |
the I expect the Perhaps we could try to fix these upstream?
Anyhow I tried this out on one of my NixOS hosts and it seems to work well. I can now easily filter out config files. Seems to work well! (Though it classifies the Perhaps it makes sense to put this option behind a flag if you're afraid of mis-classifying things? |
To match out-paths such as:
Can you clarify this? What is your toplevel derivation out-path?
I think with the addition of the out-path match requirement, it should be pretty safe. Also, as discussed, we can't make it much worse compared to how it now works, simply classifying everything as
I also hope these and similar cases would be fixed upstream. |
Set the cdx component type based on the following heuristic:
Resolves: #140