From kde-release-team Wed May 21 14:58:20 2008 From: Christian Ehrlicher Date: Wed, 21 May 2008 14:58:20 +0000 To: kde-release-team Subject: Re: Fwd: KDE 4/windows naming Message-Id: <4834388C.8060800 () gmx ! de> X-MARC-Message: https://marc.info/?l=kde-release-team&m=121138194907215 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1818160632==" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1818160632== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig51F53CC251AE27FBF70F51D9" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig51F53CC251AE27FBF70F51D9 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Patrick Spendrin schrieb: > Christian Ehrlicher schrieb: >> I somehow mixed kde-packager and release-team - hope this is now the=20 >> correct list :) >> >> >> >> ---------------------------8<-------------------- >> Hi, >> >> I'm thinking about a proper naming for the first official KDE4/windows= =20 >> release which should come with KDE4.1 when I'm correct. >> >> I would propose 'KDE 4.1/windows (alpha)'. Calling it beta would=20 >> suggest that 4.2 maybe will become stable but I don't think this is=20 >> possible with the current manpower and the short release cycle (no=20 >> discussions on the release cycle please - this is another topic). > I am not that amazed of the plan to append the alpha or beta at all but= =20 > this is just my opinion. Not adding anything would mean that it's full useable which is not the=20 case (we're imho far away from this) >> >> I won't call it beta because we've a lot of internal things to do=20 >> which most of them aren't directly visible to the user but will affect= =20 >> any KDE program running on windows: >> - the dbus-daemon uses tcp/ip which is a huge security concern. It=20 >> also doesn't distinguish between system and session, > This is one of the things that probably have to work before we could sa= y=20 > it is of beta state. >> - the communication between kded, klauncher and others work but I=20 >> think there're a lot of pitfalls in there where we're not yet aware of= =20 >> (need a wider testing) >> - the system integration for the kcm modules isn't started - I think=20 >> most of the modules which work on windows should not only affect KDE=20 >> programs. > What do you mean by this? Should the proxy kcm change the system=20 > settings proxy stuff as well? Then we'd still have a lot of work to do = =2E.. At least in the long term - you can't explain anyone why he has to add=20 proxy settings twice etc. >> - minor: a lot of apps still don't have a proper icon / the icon name = >> changed but nobody adjusted kde4_add_icon() macro :( > I want to have this fixed right before the release - this might add som= e=20 > more icons (not sure of that part) and makes sure that no more changes = > are made before the release. >> - Some shared libs are still installed into /lib instead /bin which=20 >> needs an adjustment of the PATH variable. A normal windows user can't = >> do this. > As we will have to decide about the packages that we {want to|can}=20 > distribute, this can be fixed for those packages before the release as = > well. >> - The packaging process (which currently eats most of my time... :( ) = >> needs some improvements to pack each application instead the whole=20 >> package like it's done now. > This should be a change in the way packaging works -=20 > kdewin-packager/emerge needs to be able to split up the current targets= =2E This sounds much easier than it is - do you have the time to fix it? I=20 guess not. > But this leads to another question: > If we're using an approach like that, should we distribute=20 > win32libs+Qt+kdesupport+kdelibs+kdepimlibs+kdebase-runtime as a KDE=20 > Runtime Environment / KDE Software Development Kit? We could even split= =20 > that up in a low level part containing win32libs+Qt+kdesupport and a=20 > high-level part containing only KDE stuff. I think three parts - win32libs (or 'support' libs), Qt and KDE SDK=20 (support, libs, pimlibs) - should be ok. > The installer would work in the same way as usual but Nullsoft=20 > Installers should be possible and compatible as well. This is already possible. Christian --------------enig51F53CC251AE27FBF70F51D9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkg0OIwACgkQHAIuqbOiZ+nOvwCgsE9Yd+Zkpw2vPwztTiRmM2nL sGoAoJDk+udywu7x0xBfpesDJDREb7A9 =udoI -----END PGP SIGNATURE----- --------------enig51F53CC251AE27FBF70F51D9-- --===============1818160632== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team --===============1818160632==--