Mailinglist Archive: opensuse-mingw (3 mails)
| < Previous | Next > |
Re: [opensuse-mingw] Fix for mingw32-runtime
- From: Maarten Bosmans <mkbosmans@xxxxxxxxx>
- Date: Wed, 21 Dec 2011 21:59:34 +0100
- Message-id: <CA+CvcKSaTBtF9xLiSqOERb1Qx1TPc3QwBxEXiXPRpCPiuGLu9g@mail.gmail.com>
2011/12/17 Dominik Schmidt <ich@xxxxxxxxxxxxxxxxxx>:
Are our packages up to date? Or is the fix in master/main/trunk of
mingw runtime and thus unreleased? Anyway, however you would like to
fix it (separate patch or new tarballs), it's a good idea to upload
changes to such an important package to a branched package in your
home project first and check whether it builds on all the platforms.
Perhaps this is already your workflow, in that case, please ignore my
comment.
I usually have such a change waiting for a week or so in my home repo
until a low-level package is changed by someone else and piggy back on
the repo rebuild. But especially when all the repos are build and
published, feel free to upload the changes, as the binary packages are
still available for download during the day(s) (or even weeks) of
rebuilding.
One last remark: don't forget the windows:mingw:win64 repository. I
noticed that Tomahawk isn't building correctly for win64. I don't
really care for that package, but if you are going to change
mingw-runtime, please make sure that both targets compile cleanly.
Maarten
--
To unsubscribe, e-mail: opensuse-mingw+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-mingw+owner@xxxxxxxxxxxx
Hey,
two of our Tomahawk users reported a crash on startup (before even entering
main), Kai Tietz has fixed it in the mingw runtime upstream and I would like
to have that fix in our repositories.
Are our packages up to date? Or is the fix in master/main/trunk of
mingw runtime and thus unreleased? Anyway, however you would like to
fix it (separate patch or new tarballs), it's a good idea to upload
changes to such an important package to a branched package in your
home project first and check whether it builds on all the platforms.
Perhaps this is already your workflow, in that case, please ignore my
comment.
As that will block the repository for some days probably, should I wait for
someone else to make a bigger change and block it as well so we only have
one full rebuild or just go ahead?
I usually have such a change waiting for a week or so in my home repo
until a low-level package is changed by someone else and piggy back on
the repo rebuild. But especially when all the repos are build and
published, feel free to upload the changes, as the binary packages are
still available for download during the day(s) (or even weeks) of
rebuilding.
So the question is rather: Is anyone going to commit big changes soon?
Best regards,
Dominik
One last remark: don't forget the windows:mingw:win64 repository. I
noticed that Tomahawk isn't building correctly for win64. I don't
really care for that package, but if you are going to change
mingw-runtime, please make sure that both targets compile cleanly.
Maarten
--
To unsubscribe, e-mail: opensuse-mingw+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-mingw+owner@xxxxxxxxxxxx
| < Previous | Next > |