The vixie-cron and vcron ebuilds specify the exact same package file to install (even the MD5sums are the same). Neither of them remove their initscript from /etc/init.d when they are unmerged. This means that vixie-cron won't be added to any runlevel when it is emerged the second time. Reproducible: Always Steps to Reproduce: 1. emerge vcron 2. emerge -C vcron 3. emerge vixie-cron Actual Results: The env-update step of "emerge vixie-cron," and any env-update commands thereafter give: * Service 'vcron' already provide 'cron'!; * Not adding service 'vixie-cron'... [ ok ] Expected Results: The service should have been added properly. When vixie-cron is emerged, emerge suggests running "rc-update del vcron ; rc-update add vixie-cron", but this fails with the same error as above because /etc/init.d/vcron is still present. To fix this problem delete either /etc/init.d/vcron or /etc/init.d/vixie-cron (depending on which one you want to use), then run env-update. Why are there two ebuilds for the same version of the same package?
Oops, I just read the ChangeLog for the vcron ebuild and saw why it's there (old GRP installs). Perhaps vcron should be masked, or would that also cause problems?
dave, that would cause problems unfortunately. I am planning on removing vcron from portage entirely, sometime in the first half of 2004. It'll be after we do the next release of GRP, so that installation instructions and GRP packages will all have vixie-cron. By then vcron should obsolete itself
Why not do as with Mozilla gtk2 of old, when you try to emerge recent versions of vcron have it spit out a message saying, 'switch to vixie-cron or FORCE="vcron" emerge'. That should get most people switched over to vixie-cron without causing any issues.
Also the vixie-cron ebuild states to run `rc-update add vixie-cron` which should be `rc-update add vixie-cron default`
mholzer did that, and I've removed vcron from portage.
