#!/bin/bash

# Copyright (C) 2016      by Mihai Moldovan <ionic@ionic.de>
#
# This programme is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This programme is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the
# Free Software Foundation, Inc.,
# 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.

export PATH="${HOME}/bin:${PATH}"

# ${CDPATH} could lead to some very nasty problems. Better unset it.
unset CDPATH

# Takes a Debian code name and converts it into the
# corresponding numerical version (based on year and month
# of the release.)
# The result is printed as a string with a trailing newline.
# The return code is either 0, iff mapping was successful,
# or 1 if the code name is unknown and mapping failed.

typeset -l codename
codename="${1:?"No code name provided."}"

typeset -l -i ret="0"

case "${codename}" in
	# The first version number is actually "fake",
	# but given it's a rolling release,
	# we can't really do better here.
	("sid"|"unstable") echo "9999";;

	# FIXME: add "testing" - but how? It's not really
	# a stable release on its own, but a rolling
	# release (see sid/unstable above). Yet, it differs
	# from sid/unstable by not having one unique
	# code name, but a floating one of the next
	# stable release. We know the new release number
	# beforehand, but mapping "testing" to the
	# upcoming version number means that "testing"s
	# version number itself would be floating, creating
	# problems after each new release and requiring an
	# update. On the other hand, giving "testing" a
	# fixed version number such as "999" (smaller than
	# "unstable"s, yet bigger than anything we encountered
	# so far) would create an inconsistency:
	# The "testing" code name would have a different
	# version number than the code-name-to-be-released-
	# next.
	# For now and due to the aforementioned problems,
	# I decided to not handle the "testing" code name
	# at all.
	("stretch") echo "9";;

	("jessie") echo "8";;
	("wheezy") echo "7";;
	("squeeze") echo "6";;
	("lenny") echo "5";;
	("etch") echo "4";;
	("sarge") echo "3.1";;
	("woody") echo "3.0";;
	("potato") echo "2.2";;
	("slink") echo "2.1";;
	("hamm") echo "2.0";;
	("bo") echo "1.3";;
	("rex") echo "1.2";;
	("buzz") echo "1.1";;

	(*) ret="1";;
esac

return "${ret}"