On Monday 15 April 2002 16:03, Mark Brown wrote: > > Packaging KDE is significantly more difficult than most other packaging > > tasks. KDE depends on many libraries which all have to work together, > > and compilation takes ages. > > Let me think of an example of a package which it ought to be easier to > package... Ah, yes - insight or sather.
Hmm. Well I think I myself said that testing KDE packages is difficult, it takes a lot of time to build and run/test, etc. I could claim that both those packages you mentioned were not so easy to package OTOH, look at the diffs and size... KDE3 configures, builds and installs on debian already. You don't need to fix that part. For policy compliance you change a few dirs, and well, that's it. I think packaging something is hard when it's difficult to configure and build it for your system; ie when you have to fix it. For KDE it's not like that, because KDE is portable and up-to-date software. For a clean upgrade path, I really don't know what to say!!! Just bear in mind that you don't need much of an upgrade path :) You don't need to delve into some satanic configuration files it seems. It should be quite smooth for users. Maybe running kbuildsycoca automatically might be of help, but I'm not really sure. That is covered in KDE manuals, it may be expected that user does it himself. Are there any other issues? Thanks everybody for their comments by the way. Regards, -- Eray Ozkural (exa) <[EMAIL PROTECTED]> Comp. Sci. Dept., Bilkent University, Ankara www: http://www.cs.bilkent.edu.tr/~erayo Malfunction: http://mp3.com/ariza GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
