On Oct 16 20:02, Yaakov (Cygwin/X) wrote: > On Sat, 2012-10-13 at 13:36 +0800, JonY wrote: > > I decided do a simpler split out version due to the way the source package > > is built, with w32api as a meta package. > > If required I can redo it into a single package. > > > > Preference? Comments? > > > > http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/w32api-libs/setup.hint > > http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/w32api-libs/w32api-libs-3.0b_svn5431-1-src.tar.bz2 > > http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/w32api-libs/w32api-libs-3.0b_svn5431-1.tar.bz2 > > I think the sdesc: is confusing. How about: > > sdesc: "Windows API headers" > > > http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/w32api-includes/setup.hint > > http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/w32api-includes/w32api-includes-3.0b_svn5431-1-src.tar.bz2 > > http://sourceforge.net/projects/mingw-w64/files/Cygwin%20Snapshots/dist/w32api-includes/w32api-includes-3.0b_svn5431-1.tar.bz2 > > sdesc: "Windows API import libraries" > > But wouldn't w32api-headers be a better name?
You have a point there, Yaakov. In fact, you already set a precedent with your mingw packages, Jon. We have mingw64-headers and mingw64-runtime packages. I'm not *that* sure about the runtime name, but a consistent naming sounds like a good idea. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat