Re: Tuple and changes for m68k with -malign-int
James Le Cuirot <[email protected]>
| Newsgroups | gmane.linux.ports.m68k,gmane.linux.debian.ports.68k,gmane.comp.lib.glibc.user |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 2025-05-20 at 11:39 +0200, John Paul Adrian Glaubitz wrote: > On Mon, 2025-05-19 at 22:51 +0100, James Le Cuirot wrote: > > For what it's worth, while Adrian and I are largely aligned (haha) on this > > change, myself and others in Gentoo do intend to use a new tuple. The current > > plan is to do this at the same time as time64, which we believe also requires > > new tuples, despite Debian sticking the same ones there as well. We are aware > > that other projects will require adjusting, but we'll just deal with it. > > But what's the point for doing this? Are you worried that the three users of the > port are going to have to reinstall their systems? Does this really justify carrying > patches for many other packages? Obviously, time64 affects a lot more than just m68k, and if we're doing it for that, then we might as well do it for -malign-int at the same time. I wasn't really involved in the decision, but I think it's because Gentoo is a rolling source-based distro, so ideally we need a way for users to migrate their existing systems.