From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Randolph Chung <tausq@debian.org>
Cc: Matthias Klose <doko@cs.tu-berlin.de>,
parisc-linux@lists.parisc-linux.org,
debian-hppa@lists.debian.org, debian-gcc@lists.debian.org,
m68k-build@nocrew.org
Subject: Re: [parisc-linux] gcc-3.3 configuration
Date: Thu, 22 May 2003 10:24:05 -0400 [thread overview]
Message-ID: <20030522142405.GK21858@systemhalted> (raw)
In-Reply-To: <20030521052351.GV548@tausq.org>
> Aside from the evilness of doing binNMUs of this magnitude, I doubt a
> "transition" that doesn't change the SONAME will work. As soon as the
> new libstdc++ is installed, every c++ app on the box will instantly
> break. This means if anything happens e.g. to apt during the update, the
> system will get into a very nasty state. I don't think this is worth it.
>
> If we need to change the SONAME, then there's no binary compatibility
> anyway...
>
> As willy mentioned in his other email, if other distros want binary
> compatibility, they should follow what Debian is doing (on hppa), since
> Debian was there first :-)
*Plants flag here*
c.
next prev parent reply other threads:[~2003-05-22 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 23:42 [parisc-linux] gcc-3.3 configuration Matthias Klose
2003-05-21 0:08 ` Matthew Wilcox
2003-05-21 0:08 ` Matthew Wilcox
2003-05-20 23:26 ` Alan Cox
2003-05-20 23:26 ` Alan Cox
2003-05-21 1:02 ` John David Anglin
2003-05-21 1:02 ` John David Anglin
2003-05-21 18:02 ` Grant Grundler
2003-05-21 18:02 ` Grant Grundler
2003-05-21 5:23 ` Randolph Chung
2003-05-22 14:24 ` Carlos O'Donell
2003-05-22 14:24 ` Carlos O'Donell [this message]
2003-06-22 17:28 ` Nicholas Leippe
2003-05-21 5:23 ` Randolph Chung
-- strict thread matches above, loose matches on Subject: below --
2003-05-20 23:42 Matthias Klose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030522142405.GK21858@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=debian-gcc@lists.debian.org \
--cc=debian-hppa@lists.debian.org \
--cc=doko@cs.tu-berlin.de \
--cc=m68k-build@nocrew.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox