[Bcc'd to Pierre-Jean Coudert of WinLibre; replies will go to inkscape-devel alone: I don't want to send too much unsolicited mail his way. Pierre-Jean, tu peux voir les réponses à http://sourceforge.net/mailarchive/forum.php?forum_id=36054 si tu veux, et tu peux me répondre si tu veux que je fasse suivre à inkscape-devel.]
Every now and again, we come across packaging problems on Windows, and we say "It would be good to be able to hand these problems off to distributors, as we do for a number of un*x distributions", or "Someone should create a windows package consisting of inkscape, gimp, and perhaps other gtk software, so that they can share libraries."
I've just today discovered WinLibre, which does this: http://www.winlibre.com/en/index.php
It comes in two variants: a 650kB version that allows you to select which components you want (like a net install of a gnu/linux distribution), or a 171MB version suitable for putting on a CD.
However, I don't yet know to what extent WinLibre engages in packaging activities: i.e. do they just grab the Windows binary that we provide, or do they get the source so that they can share libraries between the programs ? (If it gives any clues, the News page mentions handling package dependencies, and that it uses InnoSetup 5.0.)
Is there anything we can do to work more closely with WinLibre ?
(Another compilation of Free Software for Windows is http://www.theopencd.org/. It has a good reputation, but it doesn't yet include Inkscape, and my impression from a couple of minutes at their web site is that they just use the binaries provided by individual projects rather than do much packaging/integration work themselves. As I say, that's just an impression that may well be wrong.)
pjrm.