On Tue, Mar 2, 2010 at 3:22 AM, Dr. David Kirkby <david.kir...@onetel.net> wrote: > William Stein wrote: > >>> In some ways, I think it would be better if the patch level was >>> incremented >>> every time a change of any sort was made to a package. One could then see >> >> That is what should definitely be done. If it isn't, then the >> automatic upgrade system wouldn't work, since it would think the >> package was already installed. If you change an spkg, make sure to >> change the name. >> >> >> -- William >> > > 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 -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org -- 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
