Hi, thanks for your reply. I've already read the "development guide", but it doesn't cover the situation when a package needs "run-time" initialization on every start of "./sage" (unless I missed some description somewhere). It seems to me that there are just two features foreseen: (1) "spkg-install" which builds the package and (2) "spkg-check" which makes a "test" of a newly built package.
In general, the last step of my new "spkg-install" script (when all "binaries" have been correctly built) would be the modification of the standard "spkg/bin/sage-env" script. Now, you say that I would need to commit the changes to "Sage root", but you also say that the spkg-install" script should not modify the "Sage library". Somehow you seem to expect that after I said "./sage -i NewPackage" I would also need to "manually" commit the changes to "Sage root", Maybe I would like to propose the following ... when one calls "./sage --bdist", it should check that all "current" files are "unmodified" with respect to the repository and when it finds a modified file, it "copies" that modified file (or it asks the user to "commit" the changes before creating the new binary distribution). Thanks in advance, Best regards, Jacek. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
