Closed ccwienk closed 1 month ago
VIOLATION DESCRIPTION | NUMBER OF VIOLATIONS |
---|---|
HIGH/CRITICAL SECURITY VULNERABILITIES | 3 |
MAJOR UPDATES AVAILABLE | 0 |
LICENSE REQUIRES REVIEW | 1 |
HIGH RISK LICENSES | 10 |
RESTRICTIED LICENSE FOR ON-PREMISE DELIVERY | 0 |
Integration Tests for b387e50285746929ffc5ddf818571c79f9a65c82 run with result: Success ✅!
Integration Tests for b387e50285746929ffc5ddf818571c79f9a65c82 run with result: Success ✅!
@ccwienk I saw that we also have the installation part mentioned in the "getting started" guide. Just referencing the Readme doc in the ocm repo would be the best idea to avoid double-maintenance. But since the site/doc structure on the website slightly differs and the page should not just contain a single link, I now maintained it there, too: https://github.com/open-component-model/ocm-website/pull/302. Not ideal, I know, but before we have a final concept where and how to create and store the content that should be presented on the website, this is the only way...
Make OCM more convenient to consume for users of Arch Linux.
Note: there are different ways (and tools) to consume packages from AUR (hence just a reference to documentation rather than a concrete shellscript-snippet). I think it is safe to assume Arch Linux users will be able to consume packages from AUR without such help ;-)