-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Fernando Nasser wrote:
> IMPORTANT: please note that aot-compile should not be tied to GCJ, but
> instead be a characteristic of any Java that is capable of
> pre-compilation. QUESTION: how to accommodate the differences in
> pre-compilation mechanisms? In any case, we should try and keep the
> command names generic so if necessary one day the JVMs that are
> AOT-capable can provide alternatives for those.
I am glad you realized this. I was going to mention to the FC guys that,
for example, kaffe has talked about supporting aot. If you have kaffe,
you don't necessary need/want to use gcj.
With the integration into rpm, would it be possible to produce the gcj
support as a separate package such that upgrades from JPackage to not
trump it. All we need for this to work is to make sure we don't have any
%{version}-%{release} requirements in JPackage and instead stick to
%{version}. At least using this method release updates could be
accomplished. I don't know enough about the situation of differing
versions at this time.
- --
Sincerely,
David Walluck
<david@xxxxxxxx>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDc/YwarJDwJ6gwowRAjYfAJ0UItAT3e/mG2LfFPQqN+UpS9Mb3gCgmk08
CRHk/fMoWmQPdsPbeTm1vlw=
=1dIi
-----END PGP SIGNATURE-----
