I'm an AppFuse person that listens here and I agree wholeheartedly with
Jason. All of the linux variations have a graphical file explorer and some
unzip facility. You just do the following:
- drag the tar.gz to where you're unzipping
- ln -s /usr/local/maven-2.0.4 /usr/local/maven
- set M2_HOME=/usr/local/maven
- export PATH=${M2_HOME}/bin: .... $PATH
That works ... and you don't have to change anything.
-I put eclipse on Ubuntu using their package manager and it didn't work
directly
-I put Tomcat on Ubuntu using their package manager and it didn't work
out-the-box with AppFuse (permissions)
I'm all for "quit trying to support Linux users who don't know Linux/UNIX"
My two-cents (or Euro's)
David Whitehurst
On 12/9/06, Henning P. Schmiedehausen <[EMAIL PROTECTED]> wrote:
Carl Trieloff <[EMAIL PROTECTED]> writes:
>1. Get rpm from jpackage. Check if it is set to build natively.
> If not,
> Build it, run it through spec-gcj-convert (file attached), verify
> new spec, rebuild it, make sure it conforms to Fedora guidelines
> for everything except the release number and all, that should be
> jpackage specific. Then upload this to jpackage.
> If it is:
> Do nothing
Oh, if only you would 'do nothing'.
That is IMHO the point where your 'community' falls apart and why I'm
a strong opponent to "including Java into FLOSS distributions".
I don't want my components compiled with a half-baked, non-standards
compliant, gobbled together thing that defies any certification
because "it wants to be free". And the readiness that RedHat/Fedora
embraces that kludge because it claims to be "free".
I don't care. If you want to use Java in an "more than hobbist"
environment, you want to use one of the commercial JDKs. And if you
defy to at least compile the Java components with a certified JDK,
they are useless. Native compilation? Bulls*hit. You don't seem to
understand Java at all.
There are a number of other decisions (like insisting on ripping
perfectly well packaged software like ant or tomcat apart because they
"contain components that we have elsewhere") but trying to do native
compilation is by far the worst.
JPackage got it wrong, you got it wrong. As long as you insist on
doing it wrong, IMHO it is better to *not* do it at all.
Or at least clearly label all
"environment-that-is-not-Java-because-we-are-not-allowed-to-call-it-so"
packages so that one can get rid of them easily.
Thanks & Best regards
Henning
--
Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
