You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: