I am not completely sure that I understand how William's proposal affects the procedure for making spkgs. What I have done the last couple of times that I made an spkg update is: 1. sage -sh 2. tar xjf package.p0.spkg 3. replace src with the new version 4. (re)place files in package.p0/patches 5. edit spkg-install 6. cp -r package.p0 package.buildtry 7. run package.buildtry/spkg-install 8. test that this spkg worked out OK 9. tar cjf package.p1.spkg package/ I guess this procedure needs adjustment from step 6 onwards in William's proposal. Is "sage -spkg" going to meddle with spkg-install? Can we still recover a "source" directory from the sage -spkg produced package on which we can run sage -spkg again to obtain the same package?
In more mathematical terms, "tar cjf" and "tar xjf" are functionally two-sided inverses of each other, which makes it very transparent how one can manipulate spkgs. Does "sage -spkg" have a similar "almost inverse"? It seems to me that William's suggestion would mean that "tar xjf" definitely wouldn't do anymore. Incidentally, it seems to me that after running spkg-install, one cannot make a correct spkg from that directory anymore, because src/ is now patched. That does slow down the development cycle for spkgs a bit. Do people have smart workarounds for that? -- 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
