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

Package vs. component: we need to support this cleanly #348

Open
pombredanne opened this issue Oct 24, 2018 · 2 comments
Open

Package vs. component: we need to support this cleanly #348

pombredanne opened this issue Oct 24, 2018 · 2 comments

Comments

@pombredanne
Copy link
Member

pombredanne commented Oct 24, 2018

This is a design and discussion item carried from #345 (comment):

we have eventually package- and component-level data.
The package would be identified by the Package URL or purl fields (type, namespace, name, version, qualifiers, subpath); and the component by its name/version.
We would need to refine how we handle cases where we have data from both

@pombredanne
Copy link
Member Author

The package part should be the main focus of V4. Support for component could go in v4.1

@pombredanne pombredanne modified the milestones: version 4, version 4.1 Dec 27, 2018
@chinyeungli chinyeungli removed this from the version 4.1 milestone Jan 15, 2020
@mjherzog
Copy link
Member

I think that we have evolved to a point where each item in an inventory is a Package with a purl or not (Component). We do not need to support overlap here.

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