In article <[EMAIL PROTECTED]>,
Alex Yukhimets <[EMAIL PROTECTED]> writes:
> The most solid ground not to switch to libc6 is not instability from the
> user's point of view (may be libc6 is not that bad), but from the point of
> view of developer who's using different kind of commercial developmental
> suits.
No, that's a good reason not to install libc6 development stuff. It's not a
good reason to not install the libc6 runtime and programs that use it, which
is what we were talking about.
> Unfortunately, as far as I can see, there is no clean way to
> have both developmental trees (libc5 and libc6) on the same machine.
There cannot be a really good way, but I think they altdev packages are
about as good as possible.
