On Mon, Mar 1, 2010 at 5:15 AM, Dr. David Kirkby <david.kir...@onetel.net> wrote: > I've just been looking at the SPKG.txt for sqlite and see: > > > === sqlite-3.6.19.p0 (Mike Hansen, October 26th, 2009) === > * Updated to 3.6.19 with > http://sqlite.org/sqlite-amalgamation-3.6.19.tar.gz. > > === sqlite-3.6.17.p0 (Dan Drake, October 25th, 2009) === > * Remove obsolete Makefile.in "patch" for Cygwin, since the new > sqlite source uses autoconf. Remove special Cygwin bits from > spkg-install; we don't need the client on Cygwin, but we install it > anyway. > > Mike, who knows far more about Sage than me, has started the patch level at > 0, despite he has updated the version of sqlite. Is that what one is > supposed to do? I thought the package would be called sqlite-3.6.19, as > there have been no patches since Mike updated this.
I personally do what you expect -- start with no ".p0" at all. Then only if that packages changed do I append a ".p1", etc. I realize that this is potentially not sufficiently systematic. I would be OK with either way, and it would be useful if we decided on one way or another. Thanks for raising this question. > 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 -- 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
