Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.devel > #111798 > unrolled thread

Re: Suggestions about i386 support

Started byAndrey Rakhmatullin <wrar@debian.org>
First post2024-05-19 10:40 +0200
Last post2024-05-19 10:40 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.debian.devel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Suggestions about i386 support Andrey Rakhmatullin <wrar@debian.org> - 2024-05-19 10:40 +0200

#111798 — Re: Suggestions about i386 support

FromAndrey Rakhmatullin <wrar@debian.org>
Date2024-05-19 10:40 +0200
SubjectRe: Suggestions about i386 support
Message-ID<IFKff-enb2-5@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

On Sun, May 19, 2024 at 07:26:28AM +0000, defrag mentation wrote:
> I think some of the i386 support policies needs to be reconsidered.
> 
> Here are some suggestions:
> 
> 1. ​Move Wine-32 to amd64, and Wine-32 may be compiled to 64-bit time_t.
What will this solve?

> Wine-32 is now in currently dropped i386 DVDs/BDs, not in amd64 DVDs/BDs as it is multiarch-only now, so at least I think moving it to amd64 is needed.
I don't think this is "needed"? Unless you think all i386 packages will be
removed from Debian, which is not the plan?

> 3. For future i386 support:
> 
> If there are not enough human resources, i386 can be dropped completely as Wine-32 is moved to amd64 
Debian wine is not the only thing we want i386 libraries for.

> If someone wants to continue maintaining pure 32-bit device bootable i386, I think recompiling it to be Y2038-safe is still meaningless 
And nobody proposed it.

-- 
WBR, wRAR

[toc] | [standalone]


Back to top | Article view | linux.debian.devel


csiph-web