|
From: Jean-Michel P. <jm....@fr...> - 2002-05-08 14:32:48
|
Le Mercredi 8 Mai 2002 15:26, Hongli Lai a =E9crit : > Why don't you just use the binaries? Win32 binaries run on every Window= s > system, > so there's not much point in compiling them yourself. I wouldn't like to use the Cygwin installer because it might conflict wit= h=20 W32/Debian packages. Let me explain again what I would like to contribute= : 1) Package management - Port Debian dpkg to native Windows and compile it using mingw. This tas= k has=20 nearly been accomplished on http://debian-cygwin.sourceforge.net/bootstra= p/. dpkg is a very powerfull package system comparable to RPM on Linux. I don= 't=20 know if it is possible to compile dpkg natively under Windows using mingw= =2E - Create W32/Debian packages providing mingw core packages. - Compile Cygwin.dll using mingw. This will enable the creation of a firs= t=20 W32/Debian Cygwin.dll package. This should be possible using MSYS-1.0.7 a= nd=20 MinGW-1.1. This will allow to create W32/Debian packages and tell wether they depend= on=20 Cygwin or not. For example, we may offer Perl with depency to Cygwin and=20 another one with no depency (mingw). - Create W32/Debian packages providing Cygwin core packages. - Create a bunch of packages (Xfree / qt2 / KDE2 / Gnome). Porting has al= ready=20 been accomplised on Cygwin. Even KDE3 is on the way. - Create packages for Windows only software like Dev-C++. Nearly all GNU=20 Windows native programs should be included. 2) GUI installer W32/Debian installation should be performed within a single GUI. The=20 installation program will give access to all W32/Debian packages at once.= =20 Packages will be available on Debian mirrors. As Cygwin and mingw can co-exist, I think this project could well be achi= eved.=20 Any candidate? Help welcome. Cheers, Jean-Michel POURE |