Naming conventions for mingw32 packages?
Dear Debian Mentors,
Some time ago I noticed the mingw32 cross crompiler of Debian, namely
They saved a lot of work for me, so I decided to help to improve it.
Since I'm relatively new to Debian packaging, I need some advice.
First of all, the mingw-* packages are quite big and I don't think
this is really "debianistic". Splitting them up into smaller pieces
for each compiler, etc., could be more desirable, especially for
those who need just a gcc, no g++ etc.
For example, the unofficial Debian packages at http://debian.speedblue.org/
are split this way:
Is there any good reason to produce such big monolithic packages instead
of smaller chunks?
I'd like to create some more mingw32 packages - the development libraries,
i.e. mingw32 ports of zlib, libpng, and virtually any other package of
the GnuWin32 project (http://gnuwin32.sourceforge.net). I also plan to
cross compile libSDL, libSDL_mixer, etc. for Debian.
So here are my questions.
Should I produce one big package, such as
or should I produce smaller packages, such as
Personally, I like the smaller packages more than the big ones. If I do
so, how exactly should they be named?
Probably it's a good idea to use the usual names for development
libraries, prefixed with "mingw32-":
On the other hand one could get even closer to the original names:
I'd prefer the first one, but what's your opinion?