Alexander E. Patrakov wrote these words on 02/12/06 21:41 CST: > Randy McMurchy wrote: >>Seems I remember that we left GGV in the book because it does a >>better job at rendering some postscript docs than does Evince. But, >>I seem to recall that there was some command or argument we could >>compile Evince with which would allow it to render equally well. > > Compile Evince 0.5.0. It has this bug fixed. Just for the reference: > > No reason to keep GGV anymore.
Updating to Evince 0.5.0 requires a poppler upgrade as well. Also, the changelog for Evince says they made changes to accommodate the D-BUS-0.60 API. For these reasons, I'm hesitant to update Evince right now. To much redo testing makes it not worth it to me. I'm only a couple of weeks from starting an update of the book to GNOME-2.14.0. Lots of updates here, so I'm thinking to just hold off the Evince update until then and leave GGV as well. Alexander, Do we need to leave GGV in there until then? I remember you saying that the bug in Evince only affects a very small portion of anyone using it. I'm committing final updates to GNOME today doing cleanup. I've been carrying changes to the last of the GNOME stuff in my sandbox for quite a while now, so if you could, please let me know about GGV. Thanks. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 11:08:00 up 14 days, 19:17, 3 users, load average: 1.06, 0.94, 0.51 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
