Bugzilla Bug 16462

For some reason, the 2.9.14_beta ebuild is hanging around, and is occupying
slot
2, and the 3.0.0 ebuild occupies slot 0.  The first problem is that the 3.0.0
ebuild is not the one merged when a 'emerge privoxy' is issued.  When one
manually merges the 3.0.0 ebuild it steps all over many of the files that were
installed as part of 2.9.14 (namely init scripts, binaries).  If one gets rid
of
2.9.14 and installs 3.0.0, a careless 'emerge -u world' will cause 2.9.14 to be
merged, again, stomping on the other version's files.  The config protection
prevents the config files from one version being overwritten by the other, but
due to the changes in those same files between the two versions, you end up
with
a broken privoxy install.

Reproducible: Always
Steps to Reproduce:
1.emerge privoxy.  Then emerge the 3.0.0 ebuild.
2. Or emerge the 3.0.0 ebuild then emerge -u world
3. Attempt to start privoxy.

Actual Results:  
You get a nicely broken privoxy setup.

fixed in cvs

thx