Vitor Buitoni wrote:

> To be able to install tomcat rpm package, you must install a lot of
> other packages that tomcat depends on, first.
> I already did this once, and for me it was very time consuming and it
> wasn't easy at all. This is because JPackager can't provide some
> packages as binary packages, because of copyright restrictions. So you
> have to download the "nosrc" rpm from jpackage, download the source code
> from the software site (e.g. java.sun.com) and build the rpm from the
> scratch. Then you can install this rpm.
> The whole process might be very painful, at least for me it was, since i
> had to learn something about the rpm creation process. :-)

Yup! It is a pain
>
> So, the REAL question is :
> - Does anybody know the advantage of installing a tomcat rpm package??

You get (or should get) a neatly setup Tomcat, with all startup scripts in
place, non-root user, etc. I know, you can do it yourself, on foot, but it is
time consuming and error prone. Not to mention that you might forget or decline
to do some part of setup.

I have 14 DEC Alpha systems running Tru64 UNIX and, although I can just do a
default install to "/usr/local", I compile and package everything into it's own
SETLD packages. It make maintainince, upgrade, installation and finding my way
around MUCH easier.

So, when I make a package, I concentrate on that task alone and build in all
functionality that I can into it. Imagine a user breathing down your neck,
needing some functionality (new version of Sendmail or some such) and you
sitting at the terminal, trying to build, install and configure everything. With
packages, it is far less frustrating.

Nix.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)