On 23.06.2016 11:25, Jacob Nevins wrote: >> We provided both clients in one package back then. The reasons for >> removing the gtk3 client were "it was too experimental" and "Latest >> update of gtk+-3 libraries seem to have broken our gtk3-client >> quite completely" (your quote from #766185) >> >> I don't mind packaging the gtk3 client separately, just make up your >> mind because it must be supported if it should be part of a stable release. > > The problem in #766185 (Oct 2014, 2.4.x) was that freeciv-gtk3 seemed to > be functionally the default client in the default Debian package, or at > least people were bumping into it and its problems not by conscious > choice of a non-default client. > > The reason we settled on removal rather than separate packaging at that > time was I think because of the lack of time before impending freeze for > Jessie. I've attached my original message which considered other > options. > > I still think having freeciv-gtk2 and freeciv-gtk3 available in separate > packages is the right answer. It would be nice if Debian could promote > our default choice of client for a given version as expressed in > 'configure' (maybe a 'freeciv' metapackage?) but that's only a > nice-to-have.
We have been providing a freeciv metapackage that depends on the gtk2 client since April 2015. > Also, the Gtk3 client has improved since that time. It's not entirely > without problems, but I'm more confident in it than I was; I think we > can support the 2.5.x Gtk3 client. That sounds encouraging. Do you intend to release another version of the 2.5 series before Debian's next freeze? Then I could upload the new freeciv-client-gtk3 package together with this one. Markus
signature.asc
Description: OpenPGP digital signature
