Re: ghostscript dependancy in the autopackage

[Guy Banay]

> You could always, of course, first extract the autopackage and install
> the contained ghostscript package manually.

Sure, if you could install to /usr/local and have it Just Work (TM)
that'd be very nice.
But I already tried that before sending my first message and it
doesn't work - if autopackage finds any GS in /usr , it never gets
around to checking /usr/local .
At least on Ubuntu 5.04 (what I'm using right now), lots of packages
depend on GS and removing the GS package provided by the distro will
cause breakage.

There might be a way around it in Ubuntu and Debian by symlinking
/etc/alternatives/gs to /usr/local/gs , and in Gentoo by doing a "fake
install" of the distro-provided package (although Gentoo, being
Gentoo, will probably have the latest anyway), but I don't know about
other distros.

> PDF is generated from the PS by ghostscript.
I didn't know that, but maybe I should've guessed. Anyway, GS-ESP-8.01
(the one that's installed by default on Ubuntu 5.04) generates
readable pdf without complaining.

I should also mention that I did manage to get Lilypond installed
(that's how I know that the pdf is readable) by passing the -d flag to
the .package and <snip> , which the people in #autopackage suggested
to me as a last resort. Maybe I'm wrong, but I got the impression that
it's undesireable for normal users to pass -d flags around to
.package(s) .

 - Guy.