On 6/15/06, Steve Haflich <smh at franz.com> wrote:
> Just to make sure everyone understand the sense of `build' under
> discussion, this is the final creation of the downloadable installer
> package. This needs to be done by one developer once per release
> cycle (really a couple times to allow for testing). Selecting a
> non-free product to build the Windows install package would not
> prevent either developers or users from recompiling from source, since
> that doesn't depend on the installation package.
I'll defer to Vadim on this one since he's doing the Windows
packaging work, but for my part, I don't want to go down this road.
What mostly bothers me about using proprietary packaging
software is that it makes it harder for someone else
to do the packaging. Sure, it is still possible but it raises
the bar; it would discourage some proportion of otherwise-
interested parties.
Aside from finding a replacement for Vadim in the event
that he is unable or unwilling for any reason, it is also
foreseeable that someone creating a derived work
would want to munge the installer for their needs.
FWIW
Robert