[pkg-wine-party] RFS: the mingw-w64 toolchain

Stephen Kitt steve at sk2.org
Sat Apr 2 21:16:17 UTC 2011

On Sat, 02 Apr 2011 19:18:26 +0200, Ove Kåven <ovek at arcticnet.no> wrote:
> Den 29. mars 2011 01:08, skrev Stephen Kitt:
> > In order to upload to Debian, it would theoretically be
> > possible to upload mingw-w64 since it's "Arch: all", then upload the full
> > gcc-mingw-w64 without bootstrapping. Alternatively, bootstrapping the
> > toolchain would only require two steps (but with two passages through
> > NEW): binutils-mingw-w64, gcc-mingw-w64 in bootstrap mode, mingw-w64 as a
> > first step; then gcc-mingw-w64 in full mode (with an incremented version
> > number) and wine-gecko-1.0.0.
> Well, doesn't look like anybody else has offered to sponsor this yet, so
> I guess I could go for it.


> Which bootstrap strategy would be recommended here?

The first strategy would allow the packages to make their way into the
archive sooner, but I'm not sure what the FTP Masters' reaction would be to a
NEW package relying on an "Arch: all" package to avoid bootstrapping itself.
In addition to that, given the delays in the NEW queue just now, the second
strategy would probably have the interesting side effect that the bootstrap
packages would make it into the archive around the time Ubuntu unfreezes;
having the bootstrap package at that point would allow the toolchain to be
synced with Ubuntu. (Using the "Arch: all" shortcut would prevent that since
Ubuntu packages are always rebuilt from source.)

Thus I'd recommend the second strategy.

If the packaging meets your requirements, would it be possible for me to
join the wine party on Alioth and push my package to a git repository there?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-wine-party/attachments/20110402/2afdee93/attachment.pgp>

More information about the pkg-wine-party mailing list