Re: Debian packages of KDevelop 3.0 (Gideon) from CVS
* Norman Jordan [EMAIL PROTECTED] wrote: I have added automake1.7 to the build-depends field, and to the depends field for gideon. Thanks! Jan
Re: Debian packages of KDevelop 3.0 (Gideon) from CVS
* Sergio Rodriguez de Guzman Martinez [EMAIL PROTECTED] wrote: deb http://people.debian.org/~njordan/unstable/binary ./ deb-src http://people.debian.org/~njordan/unstable/source ./ Also not :) deb http://people.debian.org/~njordan/unstable ./binary/ deb-src http://people.debian.org/~njordan/unstable/ ./source/ BTW, would you mind zo include automake1.7 in all you Depends: lines? I'm currently downloading source to do that myself but there are others out there, who have Adrian Bunks packages installed and who will run into the same problems. Jan
Re: KDE 3.1.1 Fast as root but slow as User
* Randy Kramer [EMAIL PROTECTED] wrote: And I keep getting confused -- did Star somehow acquire the old Wordstar? And incorporated parts of it in Star Office? Nope: StarOffice was created by a guy from Germany some years back. Something like the Compaq/HP garage thingie :). He founded StarDivision and moved to Hamburg, where most of the OOo/So developer are still working (I don't think, that there are so many 'originally sun' people around). In 1999 StarDivison was bought by Sun and then they put the code under OS license. Anyway, Most of the code is still 'made' by the old StarDivision developer in Hamburg. Some other notes, regarding the 'slowliness': up to version 5.2 StarOffice had a 'integrated desktop', which came with windows manager and some other stuff (Everything in one place). This confused MSO users a lot and after 5.2 most of the stuff was removed (you can still here some users crying about that...). Just after that and some initial cleanup and 'make it run again', the code was released in october 2000 as Open Source. 6.0 is IMO still a 'recover version', making everythingwork again. A developer said (in a german newsgroup), that SO still 'starts up' a lot too many and too big libraries at startup, but that this is one place which is worked on. And AFAI see it, the real developer, who dig deep into the code, are still not really a lot and mostly the old people from StarDivision times. IIRC the calc Easteregg showed three or four people, and that's the second 'biggest' part of SO/OOo after writer. Jan
Re: KDE 3.1.1 Fast as root but slow as User
Hello, It's getting Off Topic :) * Yven Johannes Leist [EMAIL PROTECTED] wrote: (I really wonder why nobody else thought of getting rid, or least modifying the horribly annoying splashscreen before...) You can do that as well with your debian packages (and probably with every other version). Put Logo=0 into your /etc/openoffice/sofficerc. Jan
Re: Compiling Karamba
* Ralf Nolden [EMAIL PROTECTED] wrote: I'd need the sources for my woody backports, *please* :-) BTW :) deb-src http://www.katzien.de/debian ./ Packages: kisdndial - my first package, from the scratch. Some review would be wellcome :) If it is (when it will be :) ok, I would like to find a sponsor to include it into debian... kickpim - uupdate from ktown debs and changes for new qt3 packages Kisdndial is a kickerapplet, which acts as a frontend to isdnctrl and also shows you the current connection rate. Kickpim is a a kicker applet for kaddressbook, which also reminds you of birtdays and anniversarities. The deb line is only useable if you have ktown kde and libc from unstable... Currently I have no idea how to setup a clean woody 'chroot' (?)... Jan
Re: Ralf's X backport compiled with the wrong g++
* Adrian Bunk [EMAIL PROTECTED] wrote: well, considering that woody's default compiler is gcc 2.95 I don't see a reason to compile it with gcc-3.2. That would basically mean that I would need to do a woody transition to gcc-3.2 completely and there's no way I'm going to do that :-) the correct way is to do a reverse g++ transition, IOW: compile with 2.95, postfix the package names with a -gcc2.95 or a c0 (or whatever else you like) and let your library packages conflict with the g++ 3.2 compiled library packages in unstable. The same should then be done with various gnome backports: I got a couple of -c102 packages, when installing gnome2.2 from http://mirror.raw.no/ ftp.acc.umu.se/mirror/... Jan
Re: Additions to ktown repository
* Ralf Nolden [EMAIL PROTECTED] wrote: kisdndial is probably a better candidate for adding right away :-) Hey, thanks a lot! Jan, delighted
Re: Woody: XFree86 4.3 and printing stuff
* Ralf Nolden [EMAIL PROTECTED] wrote: Ok, here you go: I added XFree86 4.3 based on DannyS's build (which means it works but the windows keys on keyboards have probs currently) backported to woody with all the xft2, fontconfig and newer freetype stuff. In the same go yesterday Trolltech released Qt 3.1.2, so I rebuild that with xft2 support. Nice nice, but unfortunatelly this would uninstall my nvidia-glx Package (libmesa4 -libmesa3) :( Does anyone know if it is save to build the nvidia-glx driver with a changed debian/control? [QT] The ones in ~nolden/kde are versioned *_3.1.2-0woody1_* snoopy:/home/jan# apt-get install libqt3-mt=3:3.1.2-0woody1 Reading Package Lists... Done Building Dependency Tree... Done E: Version '3:3.1.2-0woody1' for 'libqt3-mt' was not found snoopy:/home/jan# apt-get install libqt3-mt-dev [...] libqt3-mt-dev: Depends: libqt3-mt (= 3:3.1.2-0woody1) but 3:3.1.1-4woody5 is to be installed Depends: qt3-dev-tools (= 3:3.1.2-0woody1) but 3:3.1.1-4woody5 is to be installed Seems that the -mt isn't there. At least I can't find it via apt-cache. With the X11 repository it works, but I don't want to manually install everything (as I said, I don't want the new X11), just to get the new qt. Jan
Re: Woody: XFree86 4.3 and printing stuff
* Mario Girlando [EMAIL PROTECTED] wrote: Nice nice, but unfortunatelly this would uninstall my nvidia-glx Package (libmesa4 -libmesa3) :( Does anyone know if it is save to build the nvidia-glx driver with a changed debian/control? Worked fine for me. I backed up /etc/X11/XF86Config-4, upgraded all the upgradable, then recompiled nvidia-glx and restored the config. If there are any problems I have yet to find them. Hm... You replaced the pre-depends in debian/control? Before I try out, what is the savest way, to downgrade to the old Xserver again? Apt-Pinning? Which Packages would I need to pin down to downgrade all the others? Jan, playing save...