On Mon, May 05, 2014 at 02:37:21PM +0200, Sylvain Joyeux wrote: > My use case is a provisioner, in which arbitrary names (e.g. "avahi") is > mapped to the OS proper package name (e.g."avahi-daemon"). Since the name > depends on the OS version, I do need to know. Which I currently do with a > mix of lsb_release (damn slow on Debian) and OS-specific heuristics. That > is precisely one use case for os-release. > > Debian does provide a version name for Jessie, either as 'unstable', 'sid' > or 'jessie/sid', as reported by lsb_release and contained in > /etc/debian_version. I don't understand the rationale behind not putting > the same in os-release as the whole point of os-release *is* to identify > what a tool/script is running on.
If you need your script to know which *stable* release you are running, your script will fail when you are not running a stable release. You can set VERSION to 8 to test how your script would behave whenever jessie becomes stable, but the standard is very clear: "Applications should not rely on these fields to be set." If you do not believe me, please read this: http://www.freedesktop.org/software/systemd/man/os-release.html Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
