[gentoo-amd64] Re: File collision with courier-imap and maildrop

[Duncan]

"P.V.Anthony" <pvantony@×××××××××××.sg> posted
47852216.2040600@×××××××××××.sg, excerpted below, on  Thu, 10 Jan 2008
03:35:50 +0800:

> Trying to install courier-imap and maildrop and encountering file
> collisions.
>
> Is there any way to solve this? Some way to force it?
>
> Guessing that the files are the same as courier-imap and maildrop come
> from the same main courier-mta.

There's a way (actually several) to force it, but be sure to file a bug 
on it anyway (checking first to see if one's already filed, of course).  
IOW, don't let the fact that you can force it cause you to avoid the bug 
filing step, because it /is/ a bug, and should be fixed.

1)  You can avoid the problem once with

FEATURES=-collision-protect emerge <whatever>

2) Since that one causes a possibly quite lengthy full emerge, and the 
collision-protect test happens at the end, after the package is compiled, 
right before it's actually merged, you may prefer using ebuild.  That's a 
bit more complicated as portage uses the environment (including FEATURES)
from previous steps in later calls to ebuild, so you have to edit that 
saved environment to get it to finish.

Edit ${T}/environment (see man 5 ebuild for the meaning of the ${T} 
variable) as appropriate, in this case, removing collision-protect from 
features.

ebuild /<path/to/ebuild.ebuild> merge 

(See man 1 ebuild for the ebuild command details.)

Note that unlike emerge, ebuild can't figure out where the ebuild is by 
itself.  You have to give it the full path to the ebuild, 
/${PORTDIR}/${CATEGORY}/${PN}/${PF}.ebuild .  Of course that's a bit of a 
hassle, so for trivial merges, it's easier just to use (1) above, but for 
those that take awhile, typing the full path isn't /too/ hard, especially 
not with tab-completion. =8^)

3)  If you want to have portage avoid collision-protect checking for a 
specific file, class of files, or an entire directory, by default, set 
the COLLISION_IGNORE variable in make.conf (man 5 make.conf for details).

Normally, you'll want to do the one-shot thing using methods 1 or 2, 
since you'd expect the bug you file (right?!) to be resolved before you 
have to update or remerge that package.  However, method 3 comes in handy 
in cases such as the one I had recently in the kde overlay, testing KDE4 
svn packages.  In that case, upstream (the KDE devs) were still actively 
changing files around, adding new ones, moving them to different 
packages, deleting old ones, etc, and a lot of these were non-critical 
stuff like icons and the like.  The folks running the Gentoo kde overlay 
recommended that people set FEATURES=collision-protect as a safety 
measure to avoid KDE3 and KDE4 interfering with each other, but having 
the merges stop just because an icon appeared in two different KDE4 
packages because upstream had just changed it wasn't useful, and was VERY 
frustrating.  That's where COLLISION_IGNORE comes in, as I was able to 
set it to have portage avoid the KDE4 icons dir entirely.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@l.g.o mailing list