On Tue, Mar 2, 2010 at 6:32 AM, Dr. David Kirkby
<david.kir...@onetel.net> wrote:
> William Stein wrote:
>
>>> I think you missed my point there.
>>>
>>> I was suggesting that if (for example) python 2.6.4.p7 was updated to
>>> python
>>> 2.6.5, that the patch level went from 7 to 8, so the new package would be
>>> python-2.6.5.p8. That way, the patch level gave us some idea of how often
>>> packages were updated.
>>
>> -1
>>
>> I didn't imagined you could actually have meant that; thanks for the
>> clarification. Alex's remark that the full history is available
>> anyways in any spkg is enough.
>>
>> William
>>
>
> Fair enough. I accept that.
>
> I think the main point is that whatever is used, should be used
> consistently. It is clear Mike and I were using a different method - me
> starting a new release as foobar.x.y.z, with mike using foobar.x.y.z.p0.
>
> Decide on something, document it, then us all use it. My own preference
> would be to use foobar.x.y.z when a new upstream release is used. Then when
> the first patch is added, the package becomes foobar.x.y.z.p0.
>
> But I don't particularly care, but it would be nice to know what is
> considered the right way.
I very much like your suggestion. Let's make it official:
Use foobar.x.y.z when a new upstream release is used.
Then when the first patch is added, the package
becomes foobar.x.y.z.p0.
This seems logical to me.
William
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
