From kde-windows  Sat Nov 06 12:40:13 2010
From: "Thomas Friedrichsmeier" <thomas.friedrichsmeier () ruhr-uni-bochum ! de>
Date: Sat, 06 Nov 2010 12:40:13 +0000
To: kde-windows
Subject: Re: Rant: So you want help?
Message-Id: <201011061340.16288.thomas.friedrichsmeier () ruhr-uni-bochum ! de>
X-MARC-Message: https://marc.info/?l=kde-windows&m=128904725308842
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1533865980=="

--===============1533865980==
Content-Type: multipart/signed;
  boundary="nextPart3690438.lsk1ib2tkp";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3690438.lsk1ib2tkp
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Saturday 06 November 2010, Casper van Donderen wrote:
> Everybody should take his compiler of choice

Yes, and that's exactly the philosophy I'm trying to enable with respect to=
=20
creating releases. Everybody take the compiler they care about, and only th=
at=20
one, instead of making releases artificially cumbersome by requiring to pro=
duce=20
a complete set binaries for the complete set of compilers.

> and maybe make the default
> the platform default:

To me, *personally*, GCC 32bit is the one hard requirement in the compiler=
=20
department, because an external dependency of my application supports only=
=20
MinGW on windows. And so that's why I'm willing to help with MinGW, and tha=
t's=20
why I *personally* don't care about any other compiler.

But you're right in that it's a dead-end to try to discuss one compiler=20
against another, and I see we may be getting hung up on the side issue of=20
which should be the default.

So I'll modify my proposal for yet another short-term strategy (see also [1=
])=20
to allow breaking up the release process into smaller portions:
=2D Multi-compiler support will remain in the next version of the installer=
, but=20
instead of working on point releases, the default choice of releases will b=
e=20
trimmed down to:
 * stable-latest
 * unstable-latest
 * nightly-latest
=2D These directories will differ from the current layout in that stable-la=
test=20
may contain different versions of packages for different compilers. Perhaps=
 at=20
times MinGW will be a couple versions ahead, and perhaps sometimes MSVC wil=
l=20
be some versions ahead. So once again, releases for the different compilers=
 can=20
be made independently of each other.
=2D As long as there are no binary compatibility breakages (as coming up wi=
th=20
KDE 4.6, AFAIK), this concept will even allow to create releases in a more=
=20
incremental fashion, e.g. uploading an updated kdelibs, but leaving kdegame=
s=20
at its old version until a volunteer picks up that one.
=2D Point releases will merely be archive snapshots, and will be completely=
=20
hidden from the user (and perhaps even from the mirrors). Joe User only car=
es=20
about the latest available stable/unstable/nightly releases, anyway.

I think it's still a good idea to break up the installer into one incarnati=
on=20
for each compiler, and to decide on a default. But I'll leave that for anot=
her=20
day.

Regards
Thomas

[1] http://lists.kde.org/?l=3Dkde-windows&m=3D128689460909832&w=3D2

--nextPart3690438.lsk1ib2tkp
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAkzVTK0ACgkQEKRv+5DVNhhsegCfTvcuXNyK+LNbqu+B/fhhXDe8
sgoAoJXfNxZiYNfxG6b8rY0W6yL37Gfd
=lgRu
-----END PGP SIGNATURE-----

--nextPart3690438.lsk1ib2tkp--

--===============1533865980==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-windows mailing list
Kde-windows@kde.org
https://mail.kde.org/mailman/listinfo/kde-windows

--===============1533865980==--