lfarkas at lfarkas.org
Fri Apr 17 14:33:26 UTC 2009
Farkas Levente wrote:
> Karanbir Singh wrote:
>> Farkas Levente wrote:
>>> in 5.2 there is a yum-cron in the os dir, but there is a yum-cron only
>>> in extras/x86_64 too (not in i386).
>>> at the same time in 5.3 there is no yum-cron in the os dir, but there is
>>> yum-cron only in extras/x86_64 too (not in i386).
>>> at the same time there is a yum-cron in epel-5 too.
>>> so imho it'd be useful to clean up this situation.
>> We dont really have much interest here as to what EPEL or any other
>> third party repo is doing - you will need to chase it up with them.
>> The reason why we carried it in 5.0 etc was since yum-updatesd didnt
>> really do much. If there is anyway to make yum-updatesd run its updates
>> at a specific time, that would completely remove the need / role for
>> yum-cron. Which might be the best result allaround anyway.
> may be i was not specific enough, so then the questions are:
> - in 5.2 why yum-cron in extras/x86_64 if it's in os already?
> - in 5.3 why yum-cron only in extras/x86_64 but not in extras/i386?
> imho both the above is a bug.
and one more:
- if yum-cron was removed from upstream OS do centos would like to
include it in extras?
Levente "Si vis pacem para bellum!"
More information about the CentOS-devel