Re: Using latest ghostscript ebuild

Holger Rauch wrote:
> Hi!
> 
> I downloaded a new ebuild for ghostscript that fixes a bug related to
> copying font files during ghostscript 7.05 install. Doing
> 
> emerge ghostscript-7.05.4.ebuild
> 
> from within "/usr/portage/app-text/ghostscript" leads to the following
> messages
>

<snip>

> (I simply grabbed the ebuild from the bugzilla bug page and copied it to
> the aforementioned location.) Why doesn't this approach work? Am I missing
> something?
> 
> Thanks in advance for any help!

You should, in fact, try:

emerge -p ghostscript

and see if it is aware of your build. If so, then just emerge using the 
regular syntax (without the -p). But for various reasons (missing 
digest, package version restricted or masked) that might not work so try 
this instead:

cd /usr/portage/app-text/ghostscript
ebuild ghostscript-7.05.4.ebuild fetch
ebuild ghostscript-7.05.4.ebuild unpack
ebuild ghostscript-7.05.4.ebuild compile
ebuild ghostscript-7.05.4.ebuild install
ebuild ghostscript-7.05.4.ebuild qmerge

That's exactly what emerge does, but you get specific control over the 
ebuild used this way, and it overrides any constraints such as masking 
(that's why emerge wasn't working - it thinks you're looking for an app 
literally called ghostcript-7.05.4.ebuild rather than ghostscript - you 
can see it trying to look in the "app-text/ghostscript-7.05.4" 
directory! Emerge will know to check individual ebuilds itself in the 
appropriate sub-directory and would use the latest unmasked version). 
You may get an error about a missing digest file. If so, then do:

ebuild ghostscript-7.05.4.ebuild digest

whereupon a digest file containing the correct MD5 checksum for the 
downloaded file belonging to the ebuild will be created under 
/usr/portage/app-text/ghostscript/files.

--kerframil