On Wed, Oct 29, 2003 at 06:26:48PM +0100, Jan Schulz wrote: > I'm actually not sure, what IBM offers there: They have a JDK for > "32-bit xSeries (Intel compatible)", "32-bit iSeries/pSeries", "64-bit > iSeries/pSeries", "31-bit zSeries (S/390)" and "64-bit zSeries (S/390)". > Maybe someone can enlighten me, what the 'iSeries/pSeries' is and of > the last two bits are what debian calls s390...
iSeries are what used to be called AS/400 I think (powerpc and powerpc64). pSeries are what used to be called RS/6000 systems (powerpc and powerpc64). 31-bit zSeries is s390, 64-bit zSeries is s390x. Linux runs on all of these now, I believe. > Currently eclipse is shiped mostly as 'Architecture: all', but there > are platform dependend modules (JNI -> SWT, other). Also, this libs > are not 64bit clean, which is why the libs are already not shiped as > 'Arch: any'. > > What is the recomended way to deal with that problem? Ship as > 'Architecture: powerpc i386 s390 sparc' instead of 'Arch: all' and be > done with it? Also, will eclipse, with missing dependencies (-> jdks > are not packged), move into testing? The JDK dependencies should be ignored for contrib; that's part of its definition (contrib packages can depend on things outside of Debian). Architecture, as I understand it, should be the union of those of the dependencies. So if SWT is only available on 3 architectures, eclipse should use the same Architecture field. You might want to raise the issue on -devel or ask an ftpmaster, though; I'm not entirely clear on the reasons. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]