Christian Lohmaier wrote:
You did not have a look at the script. The script converts the rpms to
deb packages.
But it's still a script vs a human.
But the point stated is that the debian developers don't provide vanilla
OOo but a patched one.
There are two sets of debs provided. One is patched, and the other
isn't. Right now I am running a non-patched deb-installed OOo 1.9.106.
Sais who? Sun will surely continue building with JDK.
Please join the jdk-tools list. This has been discussed at length. OOo
has been working with gcj for some time to make sure that any Java in
OOo runs with gcj. And we have a set of policies to Java in OOo able to
run on free JVMs. Though our emphasis, and testing is on gcj.
The java-package fetches and installs Sun's JRE
Which package is this? I haven't seen it (on either Windows or Ubuntu).
Just have a look at the script. It basically only converts the rpms to
debs using alien and installs the debs.
Alien only goes so far. I've had problems installing large packages with
alien. It's better to have the QA provided by an actual developer
testing out the package and fixing whatever needs to be fixed to make
sure it works reliably.
I don't know why it takes a script to do this, but at least it is not a
modified version of OOo.
I am running a deb-installed un-modified OOo 1.9.106.
And as I said earlier, all this, to get a more fragile product.
Naa.
In my experience, alien is fragile for large programs.
Cheers,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
