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
When updating the base types in #75 I found that the OS lists have gotten quite long in the mean time. And since AlmaLinux and Rocky Linux advertise "bug-for-bug" compatibility with RedHat, I started to wonder how much granularity we want to have in the os explorer.
Do we want this separation or should we treat RedHat more like we treat SuSE and group all Enterprise Linux derivatives under a single os value?
(Or have two explorers, one being specific and the other being more coarse?)
The text was updated successfully, but these errors were encountered:
A space-separated list of operating system identifiers in the same syntax as the ID= setting. It should list identifiers of operating systems that are closely related to the local operating system in regards to packaging and programming interfaces, for example listing one or more OS identifiers the local OS is a derivative from.
This field is optional.
Examples: for an operating system with "ID=centos", an assignment of "ID_LIKE="rhel fedora"" would be appropriate. For an operating system with "ID=ubuntu", an assignment of "ID_LIKE=debian" is appropriate.
Same time we already have os_release explorer, but parsing it requires more work. Perhaps add os_like explorer, which initially tries to read ID_LIKE and later we can add more advanced heuristics to "detect" the lineage.
When updating the base types in #75 I found that the OS lists have gotten quite long in the mean time. And since AlmaLinux and Rocky Linux advertise "bug-for-bug" compatibility with RedHat, I started to wonder how much granularity we want to have in the
os
explorer.Do we want this separation or should we treat RedHat more like we treat SuSE and group all Enterprise Linux derivatives under a single
os
value?(Or have two explorers, one being specific and the other being more coarse?)
The text was updated successfully, but these errors were encountered: