[4011] in Release_7.7_team
Re: Minutes of 2003-09-03 release teem meeting
daemon@ATHENA.MIT.EDU (Robert A Basch)
Tue Sep 9 18:38:51 2003
From: Robert A Basch <rbasch@MIT.EDU>
To: Greg Hudson <ghudson@mit.edu>
Cc: release-team@mit.edu
In-Reply-To: <200309031901.PAA27137@equal-rites.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1063147126.4219.134.camel@abulia.mit.edu>
Mime-Version: 1.0
Date: Tue, 09 Sep 2003 18:38:47 -0400
On Wed, 2003-09-03 at 15:01, Greg Hudson wrote:
> 2. Java plugin
>
> Loading the Java plugin can be slow. We would like it to live on
> local disk. One option is to put the java locker in
> local-lockers.conf (though 475MB of disk is a lot); another is to
> create an athena-mozilla-plugins package containing such binaries.
Creating a package with the plugin binaries would not be feasible,
at least for the Java plugin; the plugin directory cannot contain
only a copy of the Java plugin binary, as the resolved path is
used somehow to find other needed files from the Java runtime
environment.
Besides the locker size, there is another issue with adding the
java locker to local-lockers.conf -- the locker uses the "current"
symlink convention to point at the "real" locker for the current
version. So we would end up with /var/athena/local/java_<version>
on local disk, complicating our ability to maintain the mozilla
plugin path in the release.
Another option might be to install the Java 1.4.2 SDK or JRE from
Solaris packages and Linux rpms which are now downloadable from
Sun. For Solaris, this would replace the 1.4.0 packages we are
currently installing as symlinks to /os. For Linux, it looks like
we would still have a version-dependent path issue, as the rpm
installs under /usr/java/j2{sdk,re}<version>, though we would not
have to worry about coordinating release changes with locker
upgrades. Also, we would need to check on possible distribution
restrictions.
Bob
