<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
+1<br>
<div class="moz-signature">
<style>
.signature, .small-signature {
font-family:"Calibri","sans-serif";mso-fareast-font-family:"Times New Roman";
color:#7F7F7F;
}
.signature {
font-size:10pt;
}
.small-signature {
font-size:8pt;
}</style><br>
</div>
<div class="moz-cite-prefix">On 11-09-2015 12:43, Fabian Deutsch
wrote:<br>
</div>
<blockquote
cite="mid:CA+PVUaTRDtMr39-oCtk92mpHv87OT59T-sjttnegC2M+uzzSyQ@mail.gmail.com"
type="cite">
<pre wrap="">Hey,
I'd like to make it easier to discover what oVirt release is
installed, and what potential variant (i.e Node) is used.
Currently we are using some Node specific files to identify this "variant".
With this patch [0] I'm suggesting to add the /etc/ovirt-release file,
with the following contents:
NAME=oVirt
ID=ovirt
VERSION="4.0 (master)"
VERSION_ID=4.0
PRETTY_NAME="oVirt 4.0"
CPE_NAME="cpe:/a:ovirtproject:ovirt:4.0:dev"
VARIANT=""
VARIANT_ID=
The variables are close to what is used by Fedora and CentOS.
The variant field is left empty by default, but can be populated with
defined values for variants like Node or i.e. a container variant.
A CPE [1] is also included for convenience.
Thoughts?
- fabian
--
[0] <a class="moz-txt-link-freetext" href="https://gerrit.ovirt.org/#/c/46067/">https://gerrit.ovirt.org/#/c/46067/</a>
[1] <a class="moz-txt-link-freetext" href="http://cpe.mitre.org/">http://cpe.mitre.org/</a>
_______________________________________________
Devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Devel@ovirt.org">Devel@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/devel">http://lists.ovirt.org/mailman/listinfo/devel</a>
</pre>
</blockquote>
<br>
</body>
</html>