Re: Naming a 32-bit/64-bit specific Java package

2006-11-30 Thread Goswin von Brederlow
Ola Lundqvist <[EMAIL PROTECTED]> writes: > Hi > > On Tue, Nov 28, 2006 at 01:41:22PM +, Matthew Johnson wrote: >> 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 b

Re: Naming a 32-bit/64-bit specific Java package

2006-11-29 Thread Goswin von Brederlow
"Shaun Jackman" <[EMAIL PROTECTED]> writes: > On 11/28/06, Shaun Jackman <[EMAIL PROTECTED]> wrote: >> I'm personally leaning towards to two arch: all packages (one 32-bit, >> one 64-bit) and a meta-package which depends on the right one. I am >> considering and open to the one arch: any package t

Re: Naming a 32-bit/64-bit specific Java package

2006-11-28 Thread Shaun Jackman
On 11/28/06, Shaun Jackman <[EMAIL PROTECTED]> wrote: I'm personally leaning towards to two arch: all packages (one 32-bit, one 64-bit) and a meta-package which depends on the right one. I am considering and open to the one arch: any package though. If it affects the decision, the binary package

Re: Naming a 32-bit/64-bit specific Java package

2006-11-28 Thread Shaun Jackman
On 11/28/06, Ola Lundqvist <[EMAIL PROTECTED]> wrote: But you will have complicated dependency problems. Or at least users will install the wrong version, or do you intend to only release the 64 bit version on 64 bit systems? and the 32 bit version on 32 bit systems? I do not really see the point

Re: Naming a 32-bit/64-bit specific Java package

2006-11-28 Thread Ola Lundqvist
Hi On Tue, Nov 28, 2006 at 01:41:22PM +, Matthew Johnson wrote: ...CUT... > >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

Re: Naming a 32-bit/64-bit specific Java package

2006-11-28 Thread Andrew Haley
Matthew Johnson writes: > 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 pa

Re: Naming a 32-bit/64-bit specific Java package

2006-11-28 Thread Matthew Johnson
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.

Re: Naming a 32-bit/64-bit specific Java package

2006-11-28 Thread Ola Lundqvist
Hi On Tue, Nov 28, 2006 at 02:13:26PM +0100, Goswin von Brederlow wrote: ...CUT... > The package is architecture independent except for the > register/address size. > > So i386, m68k, ppc, mips all can use the 32bit version. > S390x, amd64, ppc64, mips64 can use the 64bit version. > > I think ha

Re: Naming a 32-bit/64-bit specific Java package

2006-11-28 Thread Goswin von Brederlow
Ola Lundqvist <[EMAIL PROTECTED]> writes: > Hi > > On Mon, Nov 27, 2006 at 10:54:11AM -0700, Shaun Jackman wrote: >> Although SWT uses Java, it is not entirely platform independent. It >> requires one jar for 32-bit architectures and one jar for 64-bit >> architectures. I could change libswt-gtk-3

Re: Naming a 32-bit/64-bit specific Java package

2006-11-28 Thread Goswin von Brederlow
"Shaun Jackman" <[EMAIL PROTECTED]> writes: > Although SWT uses Java, it is not entirely platform independent. It > requires one jar for 32-bit architectures and one jar for 64-bit > architectures. I could change libswt-gtk-3.2-java to be an > Architecture: any package -- it's currently an all pac

Re: Naming a 32-bit/64-bit specific Java package

2006-11-28 Thread Ola Lundqvist
Hi On Mon, Nov 27, 2006 at 10:54:11AM -0700, Shaun Jackman wrote: > Although SWT uses Java, it is not entirely platform independent. It > requires one jar for 32-bit architectures and one jar for 64-bit > architectures. I could change libswt-gtk-3.2-java to be an What do you mean here? Do you mean

Naming a 32-bit/64-bit specific Java package

2006-11-27 Thread Shaun Jackman
Although SWT uses Java, it is not entirely platform independent. It requires one jar for 32-bit architectures and one jar for 64-bit architectures. I could change libswt-gtk-3.2-java to be an Architecture: any package -- it's currently an all package and does not support 32-bit architectures -- bu