Bug#586291: wesnoth-1.8: Please rename to wesnoth and remove older versions

[Gerfried Fuchs]

	Hi!

* Boris Bobrov <breton.linux at gmail.com> [2010-06-18 13:33:22 CEST]:
> Against. 
> I still have some saved games and if I update, they may become broken.

 Not broken, you won't be able to continue to play them with the new
version anymore.

> There is no sense to keep wesnoth 1.6 in testing anymore, but it
> should not be replaced by new package either. 

 It will be replaced by an empty meta package that pulls in the new
version. Unfortunately there is no other way around that - but you don't
have to upgrade your wesnoth package, you can just pull in the
wesnoth-1.8 and _not_ upgrade your wesnoth package. That way you can
stick around with the old wesnoth 1.6 branch and still enjoy the
wesnoth-1.8 branch.

 See, Andreas, this is exactly what I was talking about, and which did
pop up to me for the lenny releases already, too. Not giving the
posibility to not upgrade wesnoth on dist-ugrade stage is a disservice
to the users that I do not plan to continue to carry out.

 The plan is for upgrades from lenny to squeeze: People shouldn't
upgrade the wesnoth package blindly but stick to it to avoid being
unable to continue their started campaigns. On the other hand they have
the posibility to pull in wesnoth-1.8 to be able to play mutliplayer
games on the servers. Later when they finished their 1.4 (stable) or 1.6
(current testing) campaigns they are encouraged to pull in the meta
package to automaticly pull in future upgrades without losing their old
versions (which later have to get purged explicitly). This is the same
way that postgresql works.

 Thanks,
Rhonda
-- 
"Lediglich 11 Prozent der Arbeitgeber sind der Meinung, dass jeder
Mensch auch ein Privatleben haben sollte."
        -- http://www.karriere.at/artikel/884/