Le jeudi 6 décembre 2001, à 09:57 PM, [EMAIL PROTECTED] a écrit :
> Simply changing the CLASSPATH is not good enough-- the key is to be
> able to support Java in Fink for *both* CLASSPATH and Extensions/ based
> usage.
>
[...]
> This *wouldn't* be that big of a deal, but Sun has continued to neglect
> to provide any kind of decent automatic baseline configuration crap for
> the JVM on a per user basis. I.e. if you could simply provide a
> handful of properties to the JVM at launch based on some file in the
> user's home account, this stuff would be easy to support in a fashion
> similar to the CSH stuff already in Fink. Alas, that is not the case.
>
> As Red would say, "Dumbasses."
>
> As such, for the jvm to be started with a redefined java.ext.dirs will
> require that we externally concatenate the system supplied extension
> directory path with the fink supplied extension path.
And how can we do that ? It's not only to 'java' that we need to
pass them but to all the java tools (javac & al)
Until Sun provide us with some way of configuration, I say we're
better off with adding every jar to CLASSPATH and forget about
Extensions. In fact, I just submitted a feature request about that with
some diffs at :
http://sourceforge.net/tracker/index.php?func=detail&aid=488007&group_id=17203&;
atid=367203
--
Zauc
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
