On Sun, 2003-06-22 at 12:10, [EMAIL PROTECTED] wrote:
> On 22 Jun, James Gregory wrote:
> > wait a moment. Apt won't grock dependencies that aren't packaged AFAIK.
> > So, installing libttf from source won't help it. apt should have found
> > that dependency if you just asked it to install ghostscript.
>
> No, for the same reason I'm having a trouble now: apt-get reckons freetype-2.0.3-7
> conflicts with freetype2-2.1.3-2cl. Though that looks a little suss,
> come to think of it. It's saying freetype conflicts with freetype2,
> isn't it?
ah, actually it's saying that there are files installed by both
packages, not a conflict as per the directive in the rpm spec file.
Yeah, the cl is probably an indication of it having come from connectiva
or somewhere, and that's probably the problem - connectiva will have
packaged freetype{,2} differently -- they'll include some files they
shouldn't have (IMHO). So, grab the freetype2 package for your distro
from.. somewhere (rpmfind is good like this), install it like so:
rpm -Uvh --oldpackage freetype2*
(which says upgrade, meaning that the existing package will be
uninstalled, and --oldpackage means that if you're downgrading the
package no error will be thrown). Then, hopefully apt will be able to
get freetype for you and you should be in business (or able to use
ghostview at least :))
Now, depending on how you've got stuff set up, you might need to remove
the stuff you've compiled, but cross that bridge when you get there. I
guess the other thing to do if you can't find freetype for your distro
is to grab the src rpm from redhat 9 or something and rebuild that on
your system. Just btw, I find this is generally a better plan than
filling /usr/local/ with a whole pile of non-upgradeable junk.
HTH
James.
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
