20:13 <ana> mmm, let''s review the current situation while we are on it 20:14 <ana> i have kde3 on its way, nothing really important here, if you are curious about the status: http://ana.debian.net/ana/tmp/TODO.kde3 20:14 <ana> continuing with lenny 20:15 <ana> kde 4 parts in lenny, we already uploaded the first b-d, next are kde4libs kdepimlibs and -runtime 20:15 <ana> looking at http://techbase.kde.org/Schedules/KDE4/4.1_Release_Schedule#July_8th.2C_2008:_Tag_KDE_4.1_RC_1 20:15 <ana> it should be snapshop''ed and uploaded this weekend 20:16 <ana> only that, no really need to update the rest until rc1, i think 20:16 <ana> when uploading the RC bugs needs to be addressed 20:16 <ana> some are easy, just close, some are easy too but not fun :) 20:16 <ana> (when uploading to unstable i mean) 20:16 <MoDaX> runtime licence stuff is not fun 20:17 <ana> indeed 20:17 <MoDaX> at least for me 20:17 <ana> and then after that 20:17 <ana> what kde4 apps are we puhing: 20:17 <ana> okular, ktorrent? and? 20:17 <mukidohime> Why ktorrent? 20:18 <pinotree> because it''s kool? 20:18 <mukidohime> It won''t integrate with anything. 20:18 <ana> mukidohime: maintainers decision 20:18 <ana> since maintainer is cluefull it is ok on my side 20:18 <pinotree> mukidohime: okular neither :> 20:18 <ana> well, how it sounds?
Am Montag, 30. Juni 2008 schrieb Ana Guerrero:> 20:17 ?<ana> what kde4 apps are we puhing: > 20:17 ?<ana> okular, ktorrent? and? > 20:17 ?<mukidohime> Why ktorrent? > 20:18 ?<pinotree> because it''s kool? > 20:18 ?<mukidohime> It won''t integrate with anything. > 20:18 ?<ana> mukidohime: maintainers decision > 20:18 ?<ana> since maintainer is cluefull it is ok on my side > 20:18 ?<pinotree> mukidohime: okular neither :> > 20:18 ?<ana> well, how it sounds?I have been thinking about pushing the newer ktorrent into lenny for a while as well. It does seem to work better in general and the old version is unmaintained upstream. However, I have the feeling from vague observation that some parts don''t really work or integrate well in a KDE 3 environment. This would need some more thorough testing, but if there is general interest I can address that some time (or someone else could!).
Hello, Wednesday 02 July 2008, Peter Eisentraut ra??:> However, I have the feeling from vague > observation that some parts don''t really work or integrate well in a KDE 3 > environment.I would like to hear what problems you have. Well, ktorrent 3.1 will obviously have look&field of KDE4 and it will not share cookies with KDE3 konqueror. Maybe MIME associations might be a problem (fixable). However, old ktorrent will still be available in the ktorrent2.2 package (for people who don''t want to pull 200mb+ of dependencies and run KDE4 daemons or can''t live without RSS plugin) and I''ll switch ktorrent package to 3.1 in unstable as soon ktorrent2.2 is in the archive.> This would need some more thorough testing, but if there is > general interest I can address that some time (or someone else could!).I''m looking forward to your help on this one because I don''t use KDE3 anymore. However, ktorrent 3.1 seems to work fine on Fluxbox. -- Modestas Vainius <modestas at vainius.eu> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. Url : http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20080702/c0126ca9/attachment.pgp