Re: Naming a 32-bit/64-bit specific Java package
Ola Lundqvist <opal@debian.org> writes:
> Hi
>
> On Tue, Nov 28, 2006 at 01:41:22PM +0000, 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 bit archs? It's definitely possible to
>> have different versions in the archive for different architectures.
>
> Not unless you make them arch specific, and then you do not really have any
> benefit from it anyway.
>
> If you have defined it arch: all, then that means that it will work
> on _all_ architectures (if you have fullfilled the dependencies).
> If you have something that depend on 32 vs 64 bit then it is not
> architecture independent.
>
> We could of course try to optimize and introduce a new category
> 32 bit and 64 bit, but I do not think it is that interesting to have
> that, especially if it is just a few (or one) package there.
We already have several arch:all packages that are architecture
specific for its use. You can install them everywhere (if depends even
allow that) but they won't be of use there. We also have arch:all
packages that have unfullfillable depends on some archs.
It is relatively simple to ensure the user gets the right falvour of
the package installed by using the proper depends line in the
application or through a meta pacakage that pulls in just the right
one. The details of having a -32 and -64 package will be hidden from
the user unless seh looks closely.
> Regards,
>
> // Ola
MfG
Goswin
Reply to: