JMH wrote:
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).
The latter should be (and IIRC used to be) the correct behaviour.
Note that you can also create a source distribution with './sage --sdist
...'. In that case you'd have to include your spkg (and presumably
modify spkg/standard/deps -- some kind of Makefile -- and spkg/install,
to let Sage build and install it by default) as well.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
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.
