From kde-core-devel Mon Oct 22 09:55:34 2007 From: Thiago Macieira Date: Mon, 22 Oct 2007 09:55:34 +0000 To: kde-core-devel Subject: Re: kde3 kde4 coinstallability take two Message-Id: <200710221155.40730.thiago () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=119304699410675 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1705499.xHEjIGxc5B" --nextPart1705499.xHEjIGxc5B Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Are these kdebase 3.x or kdebase/runtime 4.0 files? Em Sunday 21 October 2007 17:13:05 Sune Vuorela escreveu: > etc/xdg/menus/kde-information.menu > etc/xdg/menus/kde-settings.menu This is kdebase/workspace 4 data. It shouldn't conflict. > dunno about these. > > usr/bin/drkonqi > Only mentioned here: > > kdelibs/kdeui/kdepackages.h:"drkonqi", > kdelibs/kdeui/util/kcrash.cpp: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0// argum= ent 0 has to be drkonqi > kdelibs/kdeui/util/kcrash.cpp: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0argv[i++= ] =3D "drkonqi"; > kdelibs/kdeui/util/kcrash.cpp: =C2=A0 =C2=A0execvp("drkonqi", const_cast<= char** >( > argv )); > kdesdk/kbugbuster/backend/bug.cpp: =C2=A0 else if ( s =3D=3D "crash" || s > =3D=3D "drkonqi" ) return Crash; Hmm... I'd say drkonqi is a "runtime" application, but it's also not a hard= =20 dependency. If drkonqi cannot be launched, you simply get no crash dialog. In any case, KDE 4's drkonqi can be used with KDE 3's applications and=20 vice-versa. Actually, both should work for *any* application. > Should be rename-able - or maybe put in libexec ? It could move to libexec or it could also be part of kdebase/workspace. Technically, though, drkonqi is the perfect example of libexec application. > usr/bin/kdebugdialog > Seems to be a user application - append 4 ? No. kdebugdialog modifies a shared config file: kdebugrc. You only need one= =20 application installed: no need for both from KDE 3 and 4. I guess this is kdebase/applications instead (not workspace, not runtime).= =20 Except that distribution packagers are HIGHLY encouraged to install it. > usr/bin/kdeeject > can't find any uses of this - only mentioned where it is build and such. I guess this one could actually be removed, but I'll let K=C3=A9vin comment= on it.=20 Ejection should be handled through Solid, which in turn goes through HAL=20 where available. Where HAL isn't used, it will need to call upon an=20 executable (/usr/bin/eject), but I don't know how Solid does it. > usr/bin/kdesu > usr/bin/kdesud > seems to be used some places, but not that many. I dunno about this. > libexec? - maybe with symlinks from bin/kdesu4 to libexec? I don't know. Last I heard, trying to rename it would cause a lot of portin= g=20 trouble. Can't distributions handle this case by using an "alternatives"-style=20 approach? The proper solution would be to use D-Bus and PolicyKit. > usr/bin/khc_docbookdig.pl > usr/bin/khc_htdig.pl > usr/bin/khc_htsearch.pl > usr/bin/khc_indexbuilder > usr/bin/khc_mansearch.pl > > urgh. is htdig still used? And is it different from the kde3 versions? libexec. These should never have been placed in ${prefix}/bin because they = are=20 are not user applications. > usr/bin/khelpcenter > usr/bin/kinfocenter > Has khelpcenter changed at all - and does kde3 khelpcenter actually satis= fy > kde4 ? No comment from me. > usr/bin/klocaldomainurifilterhelper > What is this a helper for? minicli. I guess we can fix this by not requiring the helper anymore :-) > usr/bin/knetattach > user program to mount net shares of some kind. Append 4 ? It's kio_remote's wizard program. Is it even on the menu? If it's not, I'd argue this is libexec material. > usr/bin/kjobviewer Rafael, comments? This is definitely runtime material, but like the case above, is it on the= =20 menu? In fact, shouldn't the applications from kdebase/runtime be almost all in=20 libexec? > usr/bin/kprinter > usr/bin/kdeprintfax > usr/bin/imagetops > kprinter - to be moved away Indeed. kdeprintfax is an application, it shouldn't be conflicting. If it's= =20 not dropped, it should move to kdebase/applications or further down the=20 chain. kprinter -- as a command-line tool that prints PostScript input and shows a= =20 print dialog -- should be replaced with a full-fledged PostScript reader. M= y=20 take is Okular here. It takes imagetops along with it. In any case, it's not a runtime issue: KDE applications shouldn't be callin= g=20 kprinter, they should use the C++ classes. Are there any cases of KDE=20 applications using this? (These are, by definition, non-GUI applications an= d=20 KDE isn't in the business of writing them!) > usr/bin/kstart > user application to start programs with weird args. Append 4 ? I guess not, since there might be user scripts out there that use it by nam= e. =46irst of all, is this runtime material or workspace? I.e., does it work w= ith=20 other WMs than kwin? Most of this application's options are related to the window placement, so = how=20 is it communicating that information to the Window Manager? If it's native = WM=20 hints, then either kstart would work just fine in either environment. If it's using DCOP/D-Bus, then distributions will need to replace this with= a=20 shell script that detects the running environment and execs the correct one= =2E=20 Meaning: you need to rename the KDE 3 one too. > usr/bin/ksvgtopng > a dev tool, but iirc renamed by dfaure > > usr/bin/ktrash > trash handler helper. Seems to be used by kio trash. Append4? move to > libexec? It doesn't do anything when run here, so my guess is it's not a user=20 application. Move to libexec. > usr/bin/kwriteconfig > usr/bin/kreadconfig > Related programs - but seems to be not used by anything else - append 4 ? No. Overwrite the KDE 3 ones. See the other threads about KConfig issues: t= he=20 new backend is more powerful and less prone to errors. It can handle saving= =20 and storing better, without corruption. And it should technically be able to read and write KDE 3 config files too. > usr/share/desktop-directories/kde-information.directory > usr/share/desktop-directories/kde-settings-accessibility.directory > usr/share/desktop-directories/kde-settings-components.directory > usr/share/desktop-directories/kde-settings-desktop.directory > usr/share/desktop-directories/kde-settings.directory > usr/share/desktop-directories/kde-settings-hardware.directory > usr/share/desktop-directories/kde-settings-looknfeel.directory > usr/share/desktop-directories/kde-settings-network.directory > usr/share/desktop-directories/kde-settings-power.directory > usr/share/desktop-directories/kde-settings-security.directory > usr/share/desktop-directories/kde-settings-sound.directory > usr/share/desktop-directories/kde-settings-system.directory > usr/share/desktop-directories/kde-settings-webbrowsing.directory > no clue about these. Those are kcontrol's organisation menus. I have no idea if System Settings= =20 uses them. So: if it doesn't, remove them from our installation. Remove kcontrol too, = in=20 case it hasn't been removed. Alternatively, move kcontrol to an application= =20 of its own and those files along with it. Mark it as non-coinstallable -- y= ou=20 can't install KDE 4's kcontrol while you have any KDE 3. If those files are needed, then my guess is s/kde-/kde4-/ with the proper=20 matching wherever they are referenced. > Some icons under: > usr/share/icons/crystalsvg/ > usr/share/icons/hicolor/scalable/ > Can't kde3 versions be used by distributiotns? or are they planned to be > moved away? No idea. I have a vague memory that those icons weren't from the icon theme= =20 per se, but installed by applications. So we have to make sure that the=20 Oxygen version of them exists and then simply remove the icon from=20 application. > usr/share/locale/l10n/ad/entry.desktop > usr/share/locale/l10n/ad/flag.png > And similar for other locales - seems very much like the kde3 version. > Maybe they could be used by distributions? Yes, good idea. Move those to a separate package that is shared by both KDE= 3=20 and 4. (In RPM speech, those are "noarch" packages) > usr/share/sounds/KDE_* > maybe kde3 versions could be used? Same as the icons above. =2D-=20 =C2=A0 Thiago Macieira =C2=A0- =C2=A0thiago (AT) macieira.info - thiago (AT= ) kde.org =C2=A0 =C2=A0 PGP/GPG: 0x6EF45358; fingerprint: =C2=A0 =C2=A0 E067 918B B660 DBD1 105C =C2=A0966C 33F5 F005 6EF4 5358 --nextPart1705499.xHEjIGxc5B Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQBHHHOWM/XwBW70U1gRAgw0AJ0QgBJANLrO9L97ftqTCvttQwNLhACfYXMI UQExzu1kcM6eCiOYuFMEoMQ= =qfER -----END PGP SIGNATURE----- --nextPart1705499.xHEjIGxc5B--