[systemd-devel] Question on os-release

Andreas Jaeger aj at novell.com
Thu Jun 16 02:58:12 PDT 2011


On Wednesday, June 15, 2011 09:08:20 PM Lennart Poettering wrote:
> On Mon, 30.05.11 15:00, Andreas Jaeger (aj at novell.com) wrote:
> > On Monday, May 30, 2011 14:54:54 Kay Sievers wrote:
> > > On Mon, May 30, 2011 at 10:20, Andreas Jaeger <aj at novell.com> wrote:
> > > > Looking at the os-release information, I wonder how to encode in the
> > > > best way the Beta or Milestone versions of a product, e.g. "openSUSE
> > > > 12.1 Milestone 1"
> > > > 
> > > > Is this one added as part of version? e.g.:
> > > > VERSION="12.1 Milestone 1 (Codename)"
> > > > VERSION_ID="12.1 milestone 1"
> > > > 
> > > > Or is there some other logic intented to for these?
> > > 
> > > VERSION looks fine.
> > > 
> > > VERSION_ID -- usually plain version numbers have no spaces like
> > > 3.4beta7, or 3.4-rc3 to make it easy to use it in scripts or create
> > > simple-to-handle filenames from it -- but I guess it should all work.
> > 
> > The documentation says "lower-case string (mostly numeric)" but says
> > nothing about spaces. If I should change it, please update the man page.
> 
> Added that now to the man page.

So, VERSION_ID should be:
"12.1milestone1"?

> > I was also thinking whether it makes sense to have a separate SUBVERSION
> > information or whether that was overengineering ;)
> 
> Unless we have a really good usecase I would avoid adding this for now.

The handling of milestones, alphas, betas, rcs - see the above.

> > openSUSE 12.1 Milestone 1 will have the os-release now with the above
> > text, let's see whether anything fails ;)
> 
> Neat!

Andreas
-- 
 Andreas Jaeger, Program Manager openSUSE
  aj@{novell.com,suse.com,opensuse.org} Twitter/Identica: jaegerandi
   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
    GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


More information about the systemd-devel mailing list