From: Nicholas Leippe <nick@byu.edu>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] gcc-3.3 configuration
Date: Sun, 22 Jun 2003 11:28:39 -0600 [thread overview]
Message-ID: <200306221128.39787.nick@byu.edu> (raw)
In-Reply-To: <20030521052351.GV548@tausq.org>
On Tuesday 20 May 2003 11:23 pm, Randolph Chung wrote:
> > If yes, does the following approach work: Build a libstdc++5-3.3,
> > conflicting with libstdc++5 (including libstdc++ with the same soname)
> > and doing binary uploads for hppa for all libstdc++5 dependent
> > packages? (The same could be done for m68k, but the compatibility
> > argument doesn't hold as Debian seems to be the only m68k based
> > distro).
>
> 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.
>
How many critical apps are actually C++? Is the apt suite itself?
As long as /sbin/* is C, I don't see this as a showstopper for migrating to
using a superior mechanism, which imo, should be a big goal--the sooner it's
taken care of the less problematic it will be...
just a thought...
Nick
next prev parent reply other threads:[~2003-06-22 17:28 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-21 1:02 ` John David Anglin
2003-05-21 1:02 ` John David Anglin
2003-05-20 23:26 ` Alan Cox
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
2003-06-22 17:28 ` Nicholas Leippe [this message]
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=200306221128.39787.nick@byu.edu \
--to=nick@byu.edu \
--cc=parisc-linux@lists.parisc-linux.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