RE: cups ebuild error

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Not sure what the CUPS problems are about, although I agree with Chris
that the forums are a good place to look. See also if the problem has
been confirmed at bugs.gentoo.org.

> > This morning I downloaded the 1.15_r1 (or was it 1.1.15_r1) source 
> > tarball from the cups site, ran thru the install. After that, I 
> > checked whether emerge would see that cups was already 
> compiled from 
> > source on my system (Didn't off course :-/ ) Apparently the 

Use the inject feature of Portage to make Portage think that an ebuild
has been merged even if it hasn't, like so:

	emerge -i net-print/cups

You can clean it up in the usual way (it won't touch your manually
compiled CUPS):

	emerge -C net-print/cups

> > gentoo-cups-ebuild says it's version 1.1.15_R2 (although 
> cups.org only 
> > has a r1-build???).

Gentoo build maintainers may make subtle modifications to the ebuild
file itself (such as adding a command to apply a post-release patch - if
you look, you will see that two patches are applied in the src_unpack()
section - maybe that is what is causing the problem for you?). It's
still the CUPS release that you refer to. You can see what the
difference is by examining the ChangeLog:

	less /usr/portage/net-print/cups/ChangeLog

In this case, they added a missing dependency (for Ghostscript) and some
PPC specific compile options. Also, there is something in the ebuild
that makes sure the libs are correctly linked so have a look at that if
you need to use your own compiled version.

- --kerframil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6-2 (MingW32)
Comment: For info see http://www.gnupg.org

iEUEARECAAYFAj2bCTsACgkQe1jWXPxWAXIrNACeLS98LGq26AqqKeiWgLrR5bT1
mNwAmM12Ohm4KDciyrm/rZQQGW0dd5Y=
=VAtC
-----END PGP SIGNATURE-----