On Tue, 28.04.15 17:10, Stephen Gallagher ([email protected]) wrote: > + <varlistentry> > + <term><varname>VARIANT=</varname></term> > + > + <listitem><para> > + A string identifying a specific variant or edition of the > + operating system. This may be interpreted by other packages in > + order to determine a divergent default configuration. This > + field is optional and may not be implemented on all systems. > + Examples: <literal>VARIANT=Server</literal>, > + <literal>VARIANT=Embedded</literal> > + </para></listitem> > + </varlistentry> > +
Hmm, so far for some of the fields we had "human friendly" and "parseable" field pairs. For example: NAME= is the human friendly version of the parseable field ID=, and VERSION= is the human friendly version of the parseable VERSION_ID=. SHouldn't this be of the same kind? I.e. VARIANT= and VARIANT_ID= where the former is a human friendly field (example: "Server Edition") and the latter is a parseable field (example: "server")? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
