Re: Naming a 32-bit/64-bit specific Java package
On Tue, 28 Nov 2006, Goswin von Brederlow wrote:
libswt-gtk-3.2-java32
libswt-gtk-3.2-java64
libswt-gtk-3.2-java
Any other suggestions, or completely different approaches?
This seems like a really bad solution.
The package is architecture independent except for the
register/address size.
How come it depends on this and is not architecture-dependent in another
way? this seems really strange. If it's all bytecode there should be no
dependency, and if there are native libraries it surely needs to be
arch-dependent for other things.
So i386, m68k, ppc, mips all can use the 32bit version.
S390x, amd64, ppc64, mips64 can use the 64bit version.
I think having two arch:all packages is better than having 12 arch:any
packages where they fall onto two sets of identical apckages.
I'd actually go for 12 arch:any packages myself, it's an implementation
detail the users don't need to see.
Alternatively, is it possible to detect at runtime and load different
things on different architectures?
Is it possible to upload two different versions of the any package to
the different architectures? So that you get the -64 version on 64bit
archs and the -32 version on 32 bit archs? It's definitely possible to
have different versions in the archive for different architectures.
Matt
--
Matthew Johnson
http://www.matthew.ath.cx/
Reply to: