Skip to content

Conversation

@aborrero
Copy link
Contributor

The code was mixing logic with leading "/" symbol for file paths. Update the logic to always use the symbol, as that's more natural behavior.

In order to don't break current test cases in packages, for example for doc packages declaring a path-prefix without the leading "/" symbol, the symbol will be added by this new code.

At the same time, for the doc package checker in particular, a new check for the /doc/ subdirectory is introduced, which will check for things like /usr/share/doc.

While at it, some basic go unit tests are introduced.

@aborrero aborrero requested a review from debasishbsws January 14, 2026 14:29
@aborrero aborrero force-pushed the arturo-306-package-type-check branch from b2b05ff to 92c8458 Compare January 14, 2026 14:35
Copy link
Member

@debasishbsws debasishbsws left a comment

Choose a reason for hiding this comment

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

Have some questions.

@aborrero aborrero force-pushed the arturo-306-package-type-check branch from 92c8458 to 96c61c1 Compare January 14, 2026 15:57
The code was mixing logic with leading "/" symbol for file paths.
Update the logic to always use the symbol, as that's more natural behavior.

In order to don't break current test cases in packages, for example for doc
packages declaring a path-prefix without the leading "/" symbol, the symbol
will be added by this new code.

At the same time, for the doc package checker in particular, a new check for
the /doc/ subdirectory is introduced, which will check for things like /usr/share/doc.

While at it, some basic go unit tests are introduced.

Signed-off-by: Arturo Borrero Gonzalez <arturo.borrero@chainguard.dev>
@aborrero aborrero force-pushed the arturo-306-package-type-check branch from 96c61c1 to dcf9174 Compare January 14, 2026 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants