Skip to content

Add new PURL type: 'fusesoc'#740

Open
anders-ahlberg wants to merge 6 commits intopackage-url:mainfrom
anders-ahlberg:fusesoc-type
Open

Add new PURL type: 'fusesoc'#740
anders-ahlberg wants to merge 6 commits intopackage-url:mainfrom
anders-ahlberg:fusesoc-type

Conversation

@anders-ahlberg
Copy link
Copy Markdown

This change adds a type for FuseSoC cores (see https://github.com/olofk/fusesoc).

@jkowalleck jkowalleck added the PURL type: new Register a new PURL type label Nov 19, 2025
@jkowalleck jkowalleck requested a review from a team November 19, 2025 09:03
@johnmhoran
Copy link
Copy Markdown
Member

Putting aside the fact that we have not yet defined how the various test types are to behave (parse, build, roundtrip, base, advanced and so on), the test file seems to comprise 4 groups of parse, roundtrip and build test cases that are identical but for variations in namespace, name and version values. Why? A few tests meant to fail (there are none here) would be more useful and informative.

@anders-ahlberg
Copy link
Copy Markdown
Author

Oh, I was just copying the format of the tests in some other type already present, taking that for an appropriate level of effort. I'll see about adding some more.

Copy link
Copy Markdown
Member

@pombredanne pombredanne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Here are a few nits for your review... also I am not sure that the encoding of the namespace / matches the spec... can you double check?

Comment thread tests/types/fusesoc-test.json Outdated
"expected_failure_reason": null
},
{
"description": "Build test for PURL type: fusesoc",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There may be an extra space there?

Comment thread tests/types/fusesoc-test.json Outdated
"expected_failure_reason": null
},
{
"description": "Build test for PURL type: fusesoc",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extra space in the description

Comment thread types/fusesoc-definition.json Outdated
"version_definition": {
"requirement": "optional",
"native_name": "version",
"note": "The version is the semantic version of the fusesoc core. We would really like this to be required, but that breaks validation."
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure you need this comment.... The fact that version is optional is a spec thing when you want to refer to a package without mentioning a version like in the CVE schema, or when using that with a VERS. What about this:

Suggested change
"note": "The version is the semantic version of the fusesoc core. We would really like this to be required, but that breaks validation."
"note": "The version is the semantic version of the fusesoc core."

@mjherzog mjherzog changed the title Fusesoc type Add new PURL type: fusesoc Apr 13, 2026
@mjherzog mjherzog changed the title Add new PURL type: fusesoc Add new PURL type: 'fusesoc' Apr 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PURL type: new Register a new PURL type

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants