public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Eugenia Loli-Queru" <eloli@hotmail.com>
To: gentoo-dev@gentoo.org
Subject: Re:  [gentoo-dev] LibPNG Problems :(
Date: Thu, 18 Apr 2002 00:12:47 +0000	[thread overview]
Message-ID: <F157QmA9jG1JBUnqwO800009659@hotmail.com> (raw)

>Now, could you conclude your trollish rant and show me -where- does X link 
>to libpng?

I never said that X links to it. I just said that I hope that it won't need 
to rebuilt X as well, because I did so just yesterday. I am not an X expert, 
*neither* I care what links against. I just don't want to go again through 
the pain of long compilations. I did that 2 weeks ago and did so yesterday. 
No more, thank you. I need my PC to work, not to view gcc and make working 
their butt off all day *and night* as it did for these two installations.

Problem is, I never asked for this new incompatible version of libPNG. You 
are missing the point. This new version was suddenly emerged as part of the 
(I would assume...) --update world and has messed up my whole system. I 
never asked for such a mess, I just asked for an upgrade.

If these two libs were incompatible and create such problems, they should 
not have been allowed to be part of an ebuild. If this was a full 
installation of Gentoo 1.1a, that is ok, because all of gentoo will be 
linked against a certain version of libs. But I had 1.0 and when I tried to 
udpate world, the whole thing went to hell and now I am left with half apps 
that work and half that don't (plus libGL.so does not work either now :P). 
As for that script that I need to run, it does not really fixed anything. As 
I said, rebuilding the mess that the new libpng created, is not an option.

I would expect more testing to be done before releasing all these ebuilds to 
the users or have a more intelligent portage somehow to be able to avoid dll 
hell.

As the other person very well said just an hour ago:
"Right now, installing a particular Gentoo release is like nailing jelly to 
a wall...."

I would expect a 1.0 release to be really 1.0 and to know that it works and 
that it won't put my installation in such state by emerging a game or a qt 
2.x app. I need a system that I can trust. That's all.

Thank you,
Eugenia




.

_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com



             reply	other threads:[~2002-04-18  0:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18  0:12 Eugenia Loli-Queru [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-18  0:54 [gentoo-dev] LibPNG Problems :( Eugenia Loli-Queru
2002-04-18  1:12 ` Daniel Robbins
2002-04-18  5:50 ` Spider
2002-04-17 22:08 Eugenia Loli-Queru
2002-04-17 23:47 ` Spider
2002-04-18  0:09 ` Milos Negovanovic
2002-04-18 12:19 ` Kevin Hayes
2002-04-17  7:20 Eugenia Loli-Queru
2002-04-17  8:04 ` Matthew Kennedy

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=F157QmA9jG1JBUnqwO800009659@hotmail.com \
    --to=eloli@hotmail.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