Re: -= PROPOSAL =- Release sarge with amd64
On 2004-07-13 Colin Watson <cjwatson@debian.org> wrote:
> On Tue, Jul 13, 2004 at 05:04:12PM +0200, Andreas Jochens wrote:
[...]
> This is an ABI transition. In order to cope with this, all C++ library
> packages will have to be renamed to *c103, the same way that they all
> had to be renamed to *c102 when we moved to g++ 3.3.
The point is that amd64 is not released and therfore does not have a
officiall ABI that could break, no transition required.
> This took a long
> time; the experience of the last time means that we know how to do it
> gracefully, but it will still take time.
> We *will not* be moving to g++ 3.4 for sarge. It would be release
> management insanity.
> > I fail to see why the amd64 port cannot use gcc-3.4. The amd64 port
> > may use gcc-3.4 while the other architectures still use gcc-3.3.
> The required library package name changes mean that the g++ 3.4
> transition has to happen simultaneously on all architectures, or the
> result will be total madness.
AMD64 having libfooc102 which actually uses the c103 ABI and later
making a dummy transition (when the other archs make a real transition),
renaming libfooc102 to libfooc103 whitout other changes would _ugly_.
However there are no /obvious/ real problems with that.
cu andreas
--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"
Reply to: