public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William L. Thomson Jr." <wlt@obsidian-studios.com>
To: Greg Tassone <greg@tassone.net>
Cc: gentoo-java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] java, tomcat5, and AMD64
Date: Thu, 08 Jun 2006 15:00:14 -0400	[thread overview]
Message-ID: <1149793214.28230.16.camel@wlt.obsidian-studios.com> (raw)
In-Reply-To: <1149792219.8362.8.camel@tassadar>

On Thu, 2006-06-08 at 11:43 -0700, Greg Tassone wrote:
>
> Thanks for the correction.  I think it was too late for me to reply to
> anything last night. ;-)

No worries, wasn't meaning to a prude, just wanted it straight for the
record. Others sake etc.

> > I have been running Tomcat 5.5.x on production systems since February.
> > On development servers since like December. The 5.5.x ebuild and
> > resulting binaries all should be 100%...
> 
> It sounds like you're referring to your ebuild specifically, yes?

Well I hardly consider it mine. I started to un-official take over
maintaining it around December or so. When I was wondering why it was so
old. Looking to complain, and found no one to complain to. Since I
needed Tomcat, felt I needed to do something. So here we are :)

>   (Of
> course Tomcat 5.5 itself has been solid/production-quality for a long
> time now.)

Yes, but also for the record some Tomcat devs don't like us compiling
Tomcat from source. Mainly because of people running 5.0.x versions,
having problems, and making noise in the tomcat community. Not Gentoo
ones or etc. Not even sure specifically compiling related. Just another
gripe :)

Now to date, there is only one gentoo user (also a developer) who had a
freak weird occurrence with 5.5.x via ebuild in java-experimental
overlay. However I spent considerable time researching it, and seems to
be a issue with the webapp being deployed. Despite it working with
binary release of 5.5.x just fine. At some point I might have to do a
comparison on the specific versions of everything the binary is compiled
and bundled with vs compiling from source on Gentoo with latest versions
of it all.

>   This is good to know, thanks.  I may switch over to your
> ebuild on various machines in the future.

Yes, at least in theory the 5.5.x ones, latest being 5.5.17 are much
better than most others in portage. Only one being actively maintained
to my knowledge. They should be good to go, and as solid as the official
binary release versions. Ideally maybe a bit better since it might have
newer, bug free versions of compile time deps, and bundled stuff (linked
to on Gentoo).

I have not had a problem with any version of 5.5.x compiled from source
on Gentoo. From what I can tell from irc, and etc, there are a decent
amount of people using 5.5.x versions of tomcat via the ebuild without a
problem. If anyone does have any problems I will do my best to look into
and resolve.

Also for the record I am not the official maintainer just yet. Working
on that as well. Still allot of stuff inherited from previous ebuilds
and maintainers. Which will be cleaned up, and the ebuild dialed in a
bit further with regard to permissions and etc. Not to mention some
documentation on it, layout, and etc.

-- 
Sincerely,
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com

-- 
gentoo-java@gentoo.org mailing list



      reply	other threads:[~2006-06-08 19:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08  5:08 [gentoo-java] java, tomcat5, and AMD64 Trenton D. Adams
2006-06-08  5:05 ` William L. Thomson Jr.
2006-06-08  6:53   ` Trenton D. Adams
2006-06-08 13:27     ` William L. Thomson Jr.
2006-06-09  6:57       ` Trenton D. Adams
2006-06-09 14:46         ` William L. Thomson Jr.
2006-06-09 21:25           ` Trenton D. Adams
2006-06-09 21:36             ` Calvin Austin
2006-06-10  0:34   ` Trenton D. Adams
2006-06-10 23:32     ` Caster
2006-06-08  7:03 ` Greg Tassone
2006-06-08 13:34   ` William L. Thomson Jr.
2006-06-08 18:43     ` Greg Tassone
2006-06-08 19:00       ` William L. Thomson Jr. [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1149793214.28230.16.camel@wlt.obsidian-studios.com \
    --to=wlt@obsidian-studios.com \
    --cc=gentoo-java@lists.gentoo.org \
    --cc=greg@tassone.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox