[elrepo-devel] Announcement: Updated kmod-atl1e testing release (Version 1.0.0.11)

[Alan Bartlett]

On 11 April 2010 14:10, Phil Perry <phil at elrepo.org> wrote:
> Alan Bartlett wrote:
>> On 11 April 2010 12:33, Phil Perry <phil at elrepo.org> wrote:
>>> Alan Bartlett wrote:
>>>> On 10 April 2010 17:08, Alan Bartlett <ajb at elrepo.org> wrote:
>>>>> On 10 April 2010 17:00, Phil Perry <phil at elrepo.org> wrote:
>>>>>> Would this be a case that might warrant use of an epoch?
>>>>> Yes, I thought long and hard about it, but decided against using one.  ;-)
>>>> My response, above, does not deny any interested parties in attempting
>>>> to twist my arm / tweak the black cat's tail to prompt me to change my
>>>> mind . . .
>>>>
>>>> If we were to use an epoch, should it be 0 or 1?
>>>>
>>> It should be 1, I believe.
>>>
>>> Epoch: 1
>>
>> My only recall of seeing an epoch in use is with CentOS and I'm sure
>> that what I saw was a zero epoch number -- 0:whatever . . .
>>
>
> I'm not sure either, so I just tried:
>
> yum list \* | grep '0\:' and yum list \* | grep '1\:'
>
> which leads me to believe we should start at 1.
>
> /OT - SUN's JDK is interesting :D
> jdk.x86_64                                 2000:1.6.0_19-fcs

I see:

$ yum list \* | awk '$2 ~ /:/ { print $2 }' | sort | uniq | sort -k1g
plugins:
1:005-1.el5
<big snippage>
50:6.0-2.1
51:0.1e-2.el5
$

So, o.k., the epoch, when used, should start at 1. ;-)

Alan.