public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arcady Genkin <agenkin@thpoon.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Opera 6.0 final.
Date: Mon, 20 May 2002 14:07:51 -0400	[thread overview]
Message-ID: <873cwm7kw8.fsf@tea.thpoon.com> (raw)
In-Reply-To: <1021901207.30748.29.camel@seahorse.cfftechnologies.world> (Avi Schwartz's message of "20 May 2002 08:26:47 -0500")

Avi Schwartz <avi@CFFtechnologies.com> writes:

> I figured the problem out and I posted a message about a solution in
> gentoo-user.  The problem I had was not with Opera but rather with QT2. 
> Here is the message which was titled "QT dependencies problem":
>
> While investigating the reason for problems I had with Opera 6.0 final,
> I found what my problem was and it had to do with multiple libpng
> versions.
>
> Apparently, on my system, qt-2.3.2-r1 was built when only libpng-1.2.1
> was installed thus requiring libpng.so.3.
>
> Opera was built using libqt 2.x and libpng.so.2 which corresponds with
> libpng-1.0.12.
>
> Because of the different versions of libpng used by Opera and one of its
> dynamically loaded libraries (QT) it would seg fault.
>
> Since Opera is available only as a binary, to fix it, I unmerged
> libpng-1.2.1-r1, reemerged qt-2.3.2-r1 so it used the 1.0.12 version of
> libpng, and then reemerged libpng to bring version 1.2.1 back to life.
>
> Now the question:  should the dependency of qt-2 be changed so it
> requires libpng-1.0.12 rather then the generic dependency on
> media-libs/libpng and the ebuild modified to use the proper libpng
> version?

Aahhh, what a mess!..  I don't know what to do in this situation.  It
seems that specifying libpng-1.0.12 as a dependency for qt2 would
solve the problem for opera, but it may break things for something
else, so I don't like that solution.

I suggest that we leave the things the way they are, and wait it out.
This is, obviously, a problem of transition from one version of
libpng to the other, which spans outside of gentoo project.  I think
that we should leave 6.0 masked; if somebody wants 6.0 final, they can
use the static package.

Thanks for figuring this out!
-- 
Arcady Genkin
Thanks God I'm still an atheist! -- Luis Bunuel


  reply	other threads:[~2002-05-20 18:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-18  8:57 [gentoo-dev] Opera 6.0 final Arcady Genkin
2002-05-18 10:17 ` Francisco Gimeno
2002-05-18 16:10 ` Avi Schwartz
2002-05-18 17:31   ` Arcady Genkin
2002-05-18 19:56     ` Avi Schwartz
2002-05-20  6:54       ` Arcady Genkin
2002-05-20  7:10         ` Arcady Genkin
2002-05-20 13:26         ` Avi Schwartz
2002-05-20 18:07           ` Arcady Genkin [this message]
2002-05-21 13:55             ` mikepolniak
2002-05-19 13:45 ` hanez
2002-05-19 13:29   ` mikepolniak
2002-05-20  1:12     ` Arcady Genkin

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=873cwm7kw8.fsf@tea.thpoon.com \
    --to=agenkin@thpoon.com \
    --cc=gentoo-dev@gentoo.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