2009/3/15 Sune Vuorela <deb...@pusling.com>:
> I guess we are about a stage now where we need to figure out the exact steps
> how to get the kde324 migration app, kaboom, full scale tested across the
> users of experimental.
> First, we need to get a list of remaining issues that we know should get
> Then, I think we should upload a "kaboom" that does not abort
> and upload kdelibs and kdebase-workspace with appropriate patches and
> Issues in Kaboom:
> A cancel button that makes kaboom exit 1
> Maybe move kaboom from /usr/bin to /usr/lib/something, as it is not a
> application that users sholud run manually.
There is also the size calculation bug (as reported in irc) that I
hope to fix next weekend.
And also there are of course translations to be done, but this is not
important at this stage imho.
> -workspace patches:
> make kaboom run during startkde and abort if cancelled.
> -bump shlibs in kdelibs to the debian-revision moving .kde4 to .kde
> -add a conflicts in kdelibs against any workspace versions smaller than the
> patched version
> -make workspace conflict kdelibs smaller than the .kde4 to .kde version
> - maybe add a debconf notice? aboun kaboom to kdelibs ?
A debconf notice is necessary imho. And if possible, prompt the user
to abort (optionally) and switch to tty1 to do the complete upgrade,
as starting new applications in the running kde environment may be
> be prepared for bug reports.
> now. what did I miss ?
> How might I send the coaxial IRC tool to the mouse?
> You can never telnet to the system of a AT terminale for getting access over a
> 3Dfx controller.