| 1 |
> > (unmerged the other lib) |
| 2 |
> > |
| 3 |
> > emerge giflib |
| 4 |
> > cd /usr/lib |
| 5 |
> > ln -s libgif.so.4.1.3 libungif.so.4 |
| 6 |
|
| 7 |
On Tue, Nov 01, 2005 at 01:36:23AM -0700, Duncan wrote: |
| 8 |
> That works, but it's an unneeded hack. |
| 9 |
|
| 10 |
> Nothing should need to pull in libungif. It's still possible that some |
| 11 |
> old stable packages might want it. However, sticking those in |
| 12 |
> package.keyword with ~amd64 should result in a newer package that merges |
| 13 |
> fine without libungif. If it's still required, then it's time to file a |
| 14 |
> bug (check first, of course, to see if there's already been one filed on |
| 15 |
> it). |
| 16 |
|
| 17 |
grep amd64 /etc/make.conf |
| 18 |
|
| 19 |
ACCEPT_KEYWORDS="~amd64" |
| 20 |
|
| 21 |
Been ~amd64 since the day I got this laptop. |
| 22 |
|
| 23 |
The last time I hit the problem was on |
| 24 |
|
| 25 |
lrwxrwxrwx 1 root root 15 Oct 21 14:43 /usr/lib/libungif.so.4 -> |
| 26 |
libgif.so.4.1.3 |
| 27 |
|
| 28 |
when I finally got tired and created the link. |
| 29 |
|
| 30 |
Thus on Oct 21st at 13:43 (PST) you could still experience the |
| 31 |
problem as a ~amd64 type. |
| 32 |
|
| 33 |
I got slapped in the face as a small child for filing a duplicate |
| 34 |
bug. Thus I am, as an adult, unable to file bugs. :( |
| 35 |
|
| 36 |
-- |
| 37 |
Brian Litzinger |
| 38 |
-- |
| 39 |
gentoo-amd64@g.o mailing list |
Archives