-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 8 Jul 2001, Frank Meurer wrote:
[Java]
>>A library from one vendor will have classes called
>>
>>com.snakeoil.palisade.Whatever
>>
>>and another vendor will use
>>
>>com.gerbil-gratings.simphoni.Whatever
>>
> so they can't clash.
>Actually they WILL clash!
Huh?
import com.snakeoil.palisade.*;
or
import com.gerbil-gratings.simphoni.*;
There's no problem unless you mix the two.
>>com.snakeoil.palisade4_2_1.Whatever
>>com.snakeoil.palisade5_3_0.Whatever
>
>Ahrrrg!
It is a bit horrid, I agree. I don't know whether Java library vendors
are actually doing this.
It is clear to me that you cannot have two different versions of the
same Java class installed system-wide. Not unless they use different
names as above. This is exactly analogous to RPM packages where you
can't have both sed-3.02 and sed-3.03. If you want two versions of
something, one of them has to be renamed, as Mandrake and others have
done with XFree86, Qt, bash and lots of other stuff.
So the problem of having clashing versions of the same class would
simply not arise. Rpm would uninstall the old version when installing
the new.
If you deliberately want to keep using an older version for some things,
and a newer version for others, probably the best strategy is to have
one installed system-wide, one in your home directory, and change the
CLASSPATH as needed. This is the same as what you'd do with .so files,
C header files, Perl modules or whatever.
- --
Ed Avis <[EMAIL PROTECTED]>
Finger for PGP key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7SH1gIMp73jhGogoRAj78AJ92xGg6ztjrWIUefaz0iU2pjF+/jQCfQL/k
Fo6pfFcbZqUzBDNbb5jxH3I=
=qFCn
-----END PGP SIGNATURE-----
