I'm replying only to server-dev (crossposting is bad as pleople
subscribed to both list will receive the message twice).
Please subscribe to the server-dev list if you plan to deal with
developing aspects.
Athar Shiraz Siddiqui ha scritto:
If you look at apache web server's windows installer :
http://ftp.wayne.edu/apache/httpd/binaries/win32/apache_2.2.9-win32-x86-no_ssl-r2.msi
Click on "next" after opening the file... you will see that they are
using Installshield.
Thank you! Interesting.
I wonder if they obtained an Apache wide / HTTPD PMC wide license for
the product or how they dealt with this. We may ask them!
That is go to http://www.installshield.com/
that is also a commercial product just like setupbuilder.
The problem with apache is that to be able to release something from
apache the release manager need the tool to make the release.
Not every release manager use windows at all, and none of them has a
license of this commercial products, so we have to understand how other
Apache projects dealt with this.
Thank you,
Stefano
On Sun, Jul 20, 2008 at 11:12 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Athar Shiraz Siddiqui ha scritto:
Ok I wrote this depicting automation of some aspects of the install for
james:
http://techpanacea.blogspot.com/2008/07/writing-install-utility-for-james-java.html
It needs to be refined but any help from all would be great!!
If I understant if you are using SetupBuilder. It is a commercial product
and I'm not sure we can really use it to prepare our Apache Licensed
distribution or that we can use it as part of our release process :-(
Maybe other legal/policy issues expert here can help us understanding this.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
