From: Chris White <chriswhite@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] giflib and libungif hell
Date: Fri, 18 Mar 2005 07:36:44 +0900 [thread overview]
Message-ID: <423A067C.9040406@gentoo.org> (raw)
In-Reply-To: <4238ECD4.9030605@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
Michael Marineau wrote:
>However, somethings like qt, actually depend on BOTH packages. Does libungif
>actually provide something that giflib does not? Why is both needed?
>
>
I don't know why qt requires both in the first place. qt-3.3.3 (stable
on all arches) has a _builtin_ gif reader, it just tells you about the
LWZ patent (which.. doesn't matter because it's expired..). If you look
in the source tree, under src/kernel/qasyncimageio.cpp, you'll see the
code for the builtin image reader. Therefore, it really doesn't need any
at all that I can tell, but I'll leave the qt people to decide whether
or not they want to keep giflib in there, but as it stands, libungif go
bye bye.
--
Chris White <chriswhite@gentoo.org>
------------------------
Sound | Video | PPC
ChrisWhite @ irc.freenode.net
cpw @ irc.freenode.net
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-03-17 23:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 15:41 [gentoo-dev] giflib and libungif hell Chris White
2005-03-16 18:59 ` Mike Frysinger
2005-03-17 2:35 ` Michael Marineau
2005-03-17 22:36 ` Chris White [this message]
2005-03-18 0:00 ` Gregorio Guidi
2005-03-17 5:21 ` [gentoo-dev] giflib and libungif hell [solution: libungif is being removed] Chris White
2005-03-17 9:27 ` Paul Waring
2005-03-17 10:56 ` Georgi Georgiev
2005-03-17 14:39 ` Damian Kolkowski
2005-03-17 14:46 ` Mike Frysinger
2005-03-17 15:03 ` Paul Waring
2005-03-17 15:13 ` Mike Frysinger
2005-03-18 7:39 ` Chris White
2005-03-16 20:19 ` [gentoo-dev] giflib and libungif hell Dan Armak
2005-03-21 9:00 ` Martin Schlemmer
2005-03-21 9:10 ` Armando Di Cianno
2005-03-21 9:47 ` Martin Schlemmer
2005-03-21 18:22 ` Dan Armak
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=423A067C.9040406@gentoo.org \
--to=chriswhite@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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