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

Include suggestions on receipt identifiers #4

Open
homebysix opened this issue May 3, 2023 · 0 comments
Open

Include suggestions on receipt identifiers #4

homebysix opened this issue May 3, 2023 · 0 comments

Comments

@homebysix
Copy link
Contributor

Some vendors/developers may not understand the importance of the package receipt, and specifically the reverse-domain identifier used to track which packages are installed, and which files were installed by which packages.

It would be useful to write a short section with guidance on choosing a good reverse domain to use, the relationship (or lack thereof) of package versions to the corresponding payload, and context on how many popular software deployment tools leverage package identifiers and versions to determine eligibility for patching.

Thanks for considering!

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

No branches or pull requests

1 participant