--- Bob Palowoda <[EMAIL PROTECTED]> wrote:
> > On Wed, 2005-07-20 at 15:17, Torrey McMahon wrote:
> > This is a real problem when multiple copies of the
> > same interface
> > get dragged into a single processes.
> >
>
> Interesting as I'm seeing this in the kde 3.4.1
> from blastwave.
> Multiple copies of different versions of libstdc++
> compiled
> into some of the daemon process. I wonder if this
> is what is causing
> it to crash.
>
> ---Bob
Naawwhh. That is when everything isn't copied over
correctly (missing updated packages) and you end up
with apples into spaghetti instead of apples into
apple sauce.
The bigger mess is when an updated GCC isn't backward
compatible with its own historical C++ API construct
-although maybe with good intent. It is like going to
college/school only to find out your
degree/certification is no longer in high demand in
the job market upon graduation.
As for the comments about OpenSolaris working like
Debian, the Blastwave maintainers discussed this
awhile ago. Talks of >=10,000 Solaris packages and
advanced build systems echoed down the hallways of a
few German universities and Sun whiteboards. The
Mantis bug tracker shot through the roof in bug
reporting and a stable Blastwave DVD got pressed just
recently. Pkg-get was patched, and the world was saved
once again.
Debian has years of development and people-hours over
the Blastwave organization. Unfair to leverage it
against Blastwave. We learn from historical attempts
and Blastwave is not far from the curve. You also have
to look at Blastwave's current list of maintainers
versus Debian's current list (or historical list).
Yet, Blastwave's smaller number of maintainers
competes very well in the sense of a commercial
company like Redhat -- without the funding of a Redhat
franchise either. ;oP
Guess if we all had a Ph.d in something then we
wouldn't have these problems, eh?
Ken Mays
solaris.kde.org
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
_______________________________________________
opensolaris-discuss mailing list
[email protected]