-
-
Notifications
You must be signed in to change notification settings - Fork 585
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
[docs] Minor docs for apt/yum package management #4825
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bullet points read like an outline of points to make rather than an explanation of package management, but a lot of this page is written this way so I kept my suggestions small.
@@ -179,3 +179,14 @@ This is done automatically by the release build on a dedicated Windows test runn | |||
|
|||
!!!tip "We shouldn’t use this high-security keyfob approach to signing on the next go-around with the certs." | |||
It’s way too difficult to manage, and the Safenet software is atrocious. | |||
|
|||
## APT and YUM/RPM Package Management |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Learned today that APT and YUM are acronyms! 🌈⭐️
Co-authored-by: Matt Stein <m@ttste.in>
Co-authored-by: Matt Stein <m@ttste.in>
Yeah, the intent is to just expose layers of technology to people who might understand them in a time of need, rather than to actually explain everything. |
@mattstein you may want to look again to see if you approve how I handled unreachable URLs (manage.fury.io). |
@rfay Seems fine for the awkward situation that it is. In a perfect world it’d be a normal URL that could have a little lock icon next to it to indicate (with a |
The Issue
Our setup for apt/yum package management wasn't adequately explained.