On Sun, 17 May 2009 23:33:29 +0200 Robert Millan <rmh.debian....@aybabtu.com> wrote:
> Package: wnpp > Severity: wishlist > Owner: Robert Millan <rmh.debian....@aybabtu.com> > > * Package name : gcc-mingw32 > Version : 4.4 > * URL : http://gcc.gnu.org/ > * License : GPL > Programming Lang: C > Description : The GNU C compiler (cross compiler for MingW32) How is this different to a cross compiler for armel, mips, mipsel etc.? Shouldn't the binary package name be gcc-mingw32-linux-gnu or similar? > Build of GCC for MingW32. This package includes support for C for > cross-compiling to a win32 using the MingW32 runtime. > > Notes: > > - Should not be confused with the MingW32 compiler, which is a > derivative of GCC 4.2 (I think the descriptions of both packages > are clear enough, but suggestions welcome). > - Build will be made by reliing on the gcc-source package, which > removes the need to add a separate .orig.tar.gz to the archive. If we have a method for one, why not use it for all? What is different with ming? How do we have a "source package" (the ITP) without source or relying on source that is part of another package. It would be good if we could have a way of doing this, it's about time we could get cross-compilers into Debian longterm without adding yet more binary packages to the existing gcc workload. -- Neil Williams ============= http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/
pgpkCwdDQ1uth.pgp
Description: PGP signature
