I've updated the Wiki page on CreatingDists with some directions for creating and naming the various kinds of packages we'll need.

http://www.inkscape.org/cgi-bin/wiki.pl?CreatingDists

Last time we kicked butt at collecting packages for a wide range of platforms. We wish to do the same this time, and improve on this by adopting a standardized naming convention for the packages. Specifics are on the wiki page. Here's examples:

inkscape-0.37-1.win32.exe inkscape-0.37-1.i386.deb inkscape-0.37-1.athlon.deb inkscape-0.37-1.ppc.deb inkscape-0.37-1.sparc.deb inkscape-0.37-1.mdk80.i386.rpm inkscape-0.37-1.mdk80.i686.rpm inkscape-0.37-1.mdk91.i386.rpm inkscape-0.37-1.mdk91.i686.rpm inkscape-0.37-1.fc1.i386.rpm inkscape-0.37-1.fc1.i686.rpm inkscape-0.37-1.fc1.athlon.rpm inkscape-0.37-1.fc1.ppc.rpm

Employing a standard naming convention will make it clearer for people to find the package they need.

In order to put some bounds on the quantity of packages we could accumulate, let's limit the varients of a given distro to two for a given architecture - an "oldish" one for compatibility, and a "newish" one for those on the bleeding edge. Let's also limit ourselves for x86 architectures to just i386 and i686.

As a minimum, for announcing the release lets strive to have the following covered:

* A win32 package * Debian packages for i386, i686, and ppc * rh73 and rh90 packages for i386, i686, and ppc * mdk92 package for i386 * fc1 package for i386 * suse90 package for i386 * fink package for ppc

Based on our prior release I think we should have little problem meeting these base requirements. If we can get more distros and architectures, that's great!

Bryce