From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] giflib and libungif hell [solution: libungif is being removed]
Date: Thu, 17 Mar 2005 19:56:26 +0900 [thread overview]
Message-ID: <20050317105626.GB24412@ols-dell.iic.hokudai.ac.jp> (raw)
In-Reply-To: <8953a1db05031701271198e292@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]
maillog: 17/03/2005-09:27:14(+0000): Paul Waring types
> On Thu, 17 Mar 2005 14:21:29 +0900, Chris White <chriswhite@gentoo.org> wrote:
> > libungif is now being removed from the true to honor the better giflib
> > with expired LWZ patent. On this friday, I will be doing the dep
> > adjustments in the tree. I will also be creating a bug to track issues
> > with giflib not working with certain programs. I highly doubt this
> > however, and anticipate a rather clean movement (knock on wood :|).
> > Rember: this Friday, you have been warned. Speak now or forever hold
> > your peace :P.
>
> How will this effect non-dev users who already have libungif
> installed? Will it stay or be automatically unmerged? What about
> existing programs that use libungif? I'm only asking because I'm
> fairly sure I have quite a few things that depend on one or both
> libraries and I don't want them all to break come Friday.
I guess that libungif will disappear from your system on a depclean.
I believe that you will see no errors, as long as:
- You have upgraded all your packages that depend on one or the other,
because the new releases will depend only on giflib. In other words,
if libungif is not required as a dependency by anything else.
- You don't have libungif in your "world". In this case "emerge" would
complain that "there are no ebuilds to satisfy ... " when you update
your system.
--
\/ Georgi Georgiev \/ Deliberation, n.: The act of examining \/
/\ chutz@gg3.net /\ one's bread to determine which side it is /\
\/ +81(90)6266-1163 \/ buttered on. -- Ambrose Bierce, "The \/
/\ ------------------- /\ Devil's Dictionary" /\
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-17 10:56 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
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 [this message]
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=20050317105626.GB24412@ols-dell.iic.hokudai.ac.jp \
--to=chutz@gg3.net \
--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