All,
I'm curious... how married are we to the idea of distributing installers
for Windows operating systems?
I only ask because the release-build process is somewhat complicated by
having to build such installers.
Apple has moved to ARM. Windows also supports ARM, though there aren't a
huge number of such devices in circulation today. Amazon offers
ARM-based EC2 instances for a lower price than their x86-64 equivalents.
I assume one could choose to run either Linux or Windows on those.
We don't currently have any plans to support ARM. Should we? Or would it
be better to drop (direct) support for x86-64 Windows by no longer
packaging Tomcat releases as Windows installers?
Some years ago, the Apache httpd team discontinued binary packages. For
most *NIX-environments with package managers and/or easy-to-get
toolchains, that's not a big deal, but it still leaves Windows users out
in the cold. The great folks at ApacheLounge picked up the slack and
provide Windows binaries (including "installers") for httpd and several
third-party modules, including mod_jk.
Will Stewart distributes an alternative Windows Installer, but that
appears to only support the Tomcat 9.0.x version, likely because that's
the one he uses for his own personal/professional uses.
I'm wondering if it's time for the Tomcat team to discontinue in-house
Windows installer builds.
Are there other options? The installer doesn't do much beyond expand the
binary installation and set up the service. Can that be done with an
"installer" that doesn't require a complete re-build with every Tomcat
release?
It is okay to expect Windows admins to use a script to install and set
up their installation?
Thanks,
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
