| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 2005-03-21 04:00:26 -0500 Martin Schlemmer <azarah@g.o> |
| 5 |
wrote: |
| 6 |
|
| 7 |
> On Thu, 2005-03-17 at 00:41 +0900, Chris White wrote: |
| 8 |
>> So.. basically: |
| 9 |
>> |
| 10 |
>> 1) libungif and giflib both install -lgif |
| 11 |
> |
| 12 |
> Since when ??? |
| 13 |
Yes, giflib installs libgif and ungif installs libungif. So, "since |
| 14 |
always." |
| 15 |
|
| 16 |
|
| 17 |
>> 2) They don't block each other |
| 18 |
> |
| 19 |
> Why should they?? |
| 20 |
Because they at least overwrite .... (see next section) |
| 21 |
|
| 22 |
>> 3) libungif does some weird thing where it deletes the giflib header |
| 23 |
>> file |
| 24 |
>> (probably because they aren't blocking each other?) |
| 25 |
>> |
| 26 |
> |
| 27 |
> Huh??? |
| 28 |
/usr/include/gif_lib.h |
| 29 |
|
| 30 |
>> So, they pretty much install the same thing... Can I put a blocker |
| 31 |
>> on this? |
| 32 |
>> Or does someone have a valid reason why I shouldn't... |
| 33 |
>> |
| 34 |
> |
| 35 |
> I'll say because you are on crack is a good reason, but then I would |
| 36 |
> be |
| 37 |
> nasty. |
| 38 |
While not a pressing bug, imho, giflib and libungif have no reason to |
| 39 |
both be on a system (anymore, with the LZW patent being expired). |
| 40 |
They do seemingly overwrite each others files, however, and that is an |
| 41 |
issue. Things just so happen to keep working, as they are 100% |
| 42 |
compatbile, it seems (gif_lib.h seems to work from either, for either |
| 43 |
... "seems to"). |
| 44 |
|
| 45 |
__armando di cianno |
| 46 |
fafhrd@×××××.org |
| 47 |
|
| 48 |
-----BEGIN PGP SIGNATURE----- |
| 49 |
Version: GnuPG v1.2.6 (GNU/Linux) |
| 50 |
Comment: Using the GPG bundle for GNUMail |
| 51 |
|
| 52 |
iD8DBQFCPo90wgiTPLI9xhcRArjwAJ9Wuh/Wf3tSOLYsXEH9cIu3ONy/+QCfW10l |
| 53 |
h6NKwG+TDmwremPXsGLA3Wo= |
| 54 |
=bksy |
| 55 |
-----END PGP SIGNATURE----- |
| 56 |
|
| 57 |
-- |
| 58 |
gentoo-dev@g.o mailing list |
Archives