Re: [ardour-dev] ardour in Debian
On Sat, Aug 31, 2002 at 11:18:26AM -0400, Paul Davis wrote:
> This was not the only reason. Similar breakage occurs as soon as the
> user acquires a C++ library in binary format that was compiled by a
> g++ with either different options and/or a different ABI compared the
> one used to compile and link the application. If someone upgrades from
> g++ 2.95 to g++ 3.2, for example, and they fail to recompile *every*
> C++ library on their system, problems will arise sooner or later
> (depending on how many C++ apps they run and how they were built).
The irony here is that Debian has stuck to g++ 2.95 for this reason,
and is now preparing a plan for upgrading to g++ 3.2 in a sane and
consistent manner. This will cause upgrades of Debian packages to
go smoothly and correctly, but it may not work for locally compiled
programs because those don't come with sufficient dependency information.
If ardour can't be packaged for Debian, or if it links statically
with a lot of C++ libraries, then the transition is less likely to be
smooth. It's hard to be sure about this while the details are
still being worked out. Still, there's a much better chance of it
going right if ardour is simply packaged according to Debian policy,
because that's what our upgrade plan will expect.
Richard Braakman
Reply to: