Is there any particular reason why the GTK2 package is 2.15.x and not the 2.16.x release version? I realize that they are ABI compatible, but I'd like to have the fixes. In particular an erroneous warning when you use "-pedantic."
The mingw32-libxml2 package is 2.7.2 while Fedora has 2.7.3.
Just thought I'd check before making a bug.
Op maandag 04-05-2009 om 08:46 uur [tijdzone -0500], schreef Michael Cronenworth:
Is there any particular reason why the GTK2 package is 2.15.x and not the 2.16.x release version? I realize that they are ABI compatible, but I'd like to have the fixes. In particular an erroneous warning when you use "-pedantic."
The mingw32-libxml2 package is 2.7.2 while Fedora has 2.7.3.
Just thought I'd check before making a bug.
Hi,
mingw32-gtk2-2.16.1 was built recently, but isn't available yet in the rawhide repository because Fedora is now in a development freeze. If wanted, you can manually download and install it from http://koji.fedoraproject.org/koji/buildinfo?buildID=98551
The latest version of mingw32-libxml2 indeed is 2.7.2. As I have commit privileges to that package, I'll update that later today (and post a koji link when it's finished here).
Regards,
Erik van Pienbroek
-------- Original Message -------- Subject: Re: gtk2 and libxml2 need updates From: Erik van Pienbroek erik@vanpienbroek.nl To: Fedora MinGW (Windows cross-compiler) project fedora-mingw@lists.fedoraproject.org Date: 05/04/2009 09:15 AM
mingw32-gtk2-2.16.1 was built recently, but isn't available yet in the rawhide repository because Fedora is now in a development freeze. If wanted, you can manually download and install it from http://koji.fedoraproject.org/koji/buildinfo?buildID=98551
Thanks. Although it isn't a life/death situation, I don't see why we couldn't push 2.16.1 into F11 since rawhide already has it and a mingw32 package isn't going to break a release.
The latest version of mingw32-libxml2 indeed is 2.7.2. As I have commit privileges to that package, I'll update that later today (and post a koji link when it's finished here).
OK thanks.
Op maandag 04-05-2009 om 09:18 uur [tijdzone -0500], schreef Michael Cronenworth:
mingw32-gtk2-2.16.1 was built recently, but isn't available yet in the rawhide repository because Fedora is now in a development freeze. If wanted, you can manually download and install it from http://koji.fedoraproject.org/koji/buildinfo?buildID=98551
Thanks. Although it isn't a life/death situation, I don't see why we couldn't push 2.16.1 into F11 since rawhide already has it and a mingw32 package isn't going to break a release.
Well, to get past the freeze override one needs to convince at least two members of the rel-eng team that the new packages needs to be allowed. As I don't know of any fatal bugs in the gtk 2.15.5 package I don't see any reason to request a freeze override. The new gtk package will probably be pushed as an update shortly after the release of F11 anyway.
For more details about the development freeze, see http://fedoraproject.org/wiki/ReleaseEngineering/FinalFreezePolicy
The latest version of mingw32-libxml2 indeed is 2.7.2. As I have commit privileges to that package, I'll update that later today (and post a koji link when it's finished here).
OK thanks.
It's already built by now: http://koji.fedoraproject.org/koji/buildinfo?buildID=100789
Regards,
Erik van Pienbroek
-------- Original Message -------- Subject: Re: gtk2 and libxml2 need updates From: Erik van Pienbroek erik@vanpienbroek.nl To: Fedora MinGW (Windows cross-compiler) project fedora-mingw@lists.fedoraproject.org Date: 05/04/2009 10:12 AM
Well, to get past the freeze override one needs to convince at least two members of the rel-eng team that the new packages needs to be allowed. As I don't know of any fatal bugs in the gtk 2.15.5 package I don't see any reason to request a freeze override. The new gtk package will probably be pushed as an update shortly after the release of F11 anyway.
I understand the package freeze but here's my rationale:
1) MinGW support is an official feature *starting* with Fedora 11. This means that new users will not have any mingw32 packages to start with and when they go to start to use it they will have out of date and out of sync packages. Not everyone has internet access readily available. 2) MinGW packages should ideally match the version level in Fedora. 3) Requiring an update from the get-go for this package is frivolous.
If you do not wish to create a rel-eng request ticket, I would like to. This is just a harmless/preventative package request. Same goes for libxml2.
OK thanks.
It's already built by now: http://koji.fedoraproject.org/koji/buildinfo?buildID=100789
Thank you.
Michael Cronenworth wrote:
- Requiring an update from the get-go for this package is frivolous.
It's quite common practice actually. For example, the whole KDE was updated to 4.1.3 around the day of the F10 release and we're planning to do the same with 4.2.3 and F11. Other packages also work that way.
The advantages of pushing stuff as updates on release day: * it can't break the live images or the installer, * there are 1-2 extra weeks for testing/fixing (the time between the RC composes and the first update push), * it's possible to go through updates-testing (e.g. KDE 4.1.3 went to updates-testing in the first F10 update push and to the stable updates in the second).
The drawback is that they don't get included on the live images and the installer DVD, but need to get updated by the user post-install, but that's not a big issue for the mingw32-* packages because they aren't on the live images or the installer DVD anyway, at worst this can affect custom spins including those packages but not including updates.
Kevin Kofler
-------- Original Message -------- Subject: Re: gtk2 and libxml2 need updates From: Kevin Kofler kevin.kofler@chello.at To: fedora-mingw@lists.fedoraproject.org Date: 05/04/2009 01:11 PM
not a big issue for the mingw32-* packages because they aren't on the live images or the installer DVD anyway
I was not aware of that piece of information. My original thought was that they were on the DVD. My point is moot then. Sorry for the trouble.
P.S. You can't draw an analogy between MinGW and KDE. They're completely different. The most significant difference is that MinGW is a *new* feature and KDE is not. Wouldn't you rather have a working, up-to-date feature be released? (I guess not though. *cough* KDE 4.0) I'm not a fan of bad analogies so I thought I'd throw this out there.
Michael Cronenworth wrote:
The most significant difference is that MinGW is a *new* feature and KDE is not.
Well, it's advertised as a "new feature" in F11 due to how our feature process works, but that's not really true, it's already available in F10 updates. It's not on the F10 installer images, but it's not on the F11 installer images either, so in both cases you have to get it from the repository.
Kevin Kofler
On Mon, May 04, 2009 at 10:25:36AM -0500, Michael Cronenworth wrote:
- MinGW packages should ideally match the version level in Fedora.
We have some tools that Dan Berrange wrote which should enforce this (or at least persistently email everyone when it's not the case). A to-do is to roll out those tools somewhere ...
Rich.