[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#154950: Gnome 2 transition



Package: tech-ctte

Hi,

there's a nice flameware in debian-gtk-gnome about how to handle
the transition to Gnome2.
http://lists.debian.org/debian-gtk-gnome/2002/debian-gtk-gnome-200207/threads.html


The problem :
-------------

Even though upstream have released Gnome 2.0 to the wide public, some
uystream people still think that Gnome 2 is not yet ready to be imposed to
our unstable users. 


Current situtation :
--------------------

We have some core Gnome2 package in experimental. They have a
"2" suffix. We have gnome-terminal and sawfish for Gnome 2 in
unstable (without the "2" suffix). That means we also have some basic
Gnome2 libs in unstable (it's not a problem, they coexist nicely with
Gnome1 libs).  But we don't have things like new panel and so on in
unstable. And it's those which are causing problems because they are not
made to coexist.


The conflicting solutions :
---------------------------

* Solution one :

Upload Gnome2 in unstable by replacing the old Gnome1.4 but make sure
that Gnome 1.4 is kept in sarge until G2D finalizes in unstable. 
An announce on -devel-announce before doing it would be made to inform
people that to keep Gnome 1.4 they have to make sure to use sarge.
If Gnome 1.4 absolutely needs to be maintained in the mean time,
we can use testing-proposed-updates.
http://lists.debian.org/debian-gtk-gnome/2002/debian-gtk-gnome-200207/msg00343.html

* Solution two :

Upload some Gnome2 packages in unstable with a new name (adding a "2"
suffix) so that unstable users can choose to install Gnome 2 or Gnome
1.4. Ask the user to test *2 packages. Rename them later and move them
to sarge.
http://lists.debian.org/debian-gtk-gnome/2002/debian-gtk-gnome-200207/msg00460.html

* Solution three :

This solution has not really been supported by anyone but I mention it here
for completeness because it may well turn out to be the best solution.

Work out Gnome 2 in a separate staging area (without any "2" suffix), and
move it to unstable one day (you have to define what is the criterion
for defining that "one day" because people won't agree otherwise).

That means that someone will have to handle that staging area. It also
means that G2D will be less tested on unpopular architectures.



A last note, I know that the tech-ctte takes quite some time to take a
decision, it would be great if you could try to do better this time ;-)

Thanks,
-- 
Raphaël Hertzog -+- http://strasbourg.linuxfr.org/~raphael/
Formation Linux et logiciel libre : http://www.logidee.com



Reply to: