Anonymous avatar Anonymous committed 8ab6766

un-spkg-ification complete, let's call this 2.0

Comments (0)

Files changed (4)

 include sagetexpackage.sage
 include sagetexparse.py
 include sagetex.sty
-include README.spkg
-include spkg-install
 	makeindex -s gglo.ist -o $(pkg).gls $(pkg).glo 
 	makeindex -s gind.ist -o $(pkg).ind $(pkg).idx
 	latex $(pkg).dtx
+	sage $(pkg).sage
+	latex $(pkg).dtx
 	pdflatex $(pkg).dtx
 	latex example.tex
 	sage example.sage
 	clear
 	./test
 
-# make a spkg for Sage
-spkg:
-	python setup.py sdist --formats=bztar
-	cd dist
-	gunzip dist/sagetex-$(ver).tar.gz
-	bzip2 dist/sagetex-$(ver).tar
-	cp dist/sagetex-$(ver).tar.bz2 dist/sagetex-$(ver).spkg
+# make a source distribution, used for building the spkg
+dist: all
+	python setup.py sdist --formats=tar

sagetexpackage.dtx

 % \iffalse meta-comment
 %
-% Copyright (C) 2008 by Dan Drake <ddrake@member.ams.org>
+% Copyright (C) 2009 by Dan Drake <ddrake@member.ams.org>
 % -------------------------------------------------------
 %
 % See the "Copying and licenses" section at the end of this file for the
 %<latex>\NeedsTeXFormat{LaTeX2e}
 %<latex>\ProvidesPackage{sagetex}
 %<*latex>
-  [2008/12/18 v2.0 embedding Sage into LaTeX documents]
+  [2008/01/09 v2.0 embedding Sage into LaTeX documents]
 %</latex>
 %<*driver>
 \documentclass{ltxdoc}
 % \changes{v2.0}{2008/12/16}{External Python scripts for parsing
 % SageTeX-ified documents, tons of documentation improvements,
 % sagetex.py refactored, include in Sage as spkg}
+% \changes{v2.0}{2009/01/09}{Miscellaneous fixes, final 2.0 version.}
 %
 % \GetFileInfo{sagetexpackage.dtx}
 %
 % you have defined the Sage variable |foo| to be $12$ (using, say, the
 % |sageblock| environment), then you can do something like this:
 % \begin{quote}
-% |The prime factorization of the current page plus foo is|\\
-% |$\sage{factor(foo + \thepage)}$|.
+% |The prime factorization of the current page number plus foo|\\
+% |is $\sage{factor(foo + \thepage)}$|.
 % \end{quote}
 % Here, I'll do just that right now: the prime factorization of the
-% current page plus $12$ is $\sage{factor(\thepage + 12)}$.
-%
-% The |\sage| command doesn't automatically use math mode for its
-% output, so be sure to use dollar signs or a displayed math environment
+% current page number plus $12$ is $\sage{factor(\thepage + 12)}$.
+% (Wrong answer? See footnote.\footnote{Is the above factorization
+%   wrong? If the current page number plus $12$ is one larger than the
+%   claimed factorization, you need to do another Sage/\LTX cycle on
+%   this source file. Why? The first time you run \LTX on this file, the
+%   sine graph isn't available, so the text where I've talked about the
+%   prime factorization is back one page. Then you run Sage, and it
+%   creates the sine graph and does the factorization. When you run \LTX
+%   again, the sine graph pushes the text onto the next page, but it
+%   uses the Sage-computed value from the previous page. Meanwhile, the
+%   |.sage| file has been rewritten with the correct page number, so if
+%   you do another Sage/\LTX cycle, you'll get the correct value
+%   above.}) The |\sage| command doesn't automatically use math mode for
+% its output, so be sure to use dollar signs or a displayed math
+% environment
 % as appropriate.\\
 %
 % \DescribeMacro{\percent} If you are doing modular arithmetic or string
 % \url{http://creativecommons.org/licenses/by-nc-sa/3.0/} or send a
 % letter to Creative Commons, 171 Second Street, Suite 300, San
 % Francisco, California, 94105, USA.
+%
 % \iffalse
-%   I've run into a situation where the index wants to start on the very
-%   last line of the page, and I actually get errors: ``Package multicol
-%   Error: Error saving partial page.'' The problem goes away if I
-%   fiddle with some lines so that the index starts elsewhere. Putting
-%   in a clearpage below makes the index start nicely in the middle of a
-%   page (until my change history gets too long!) and solves all those
-%   problems. It can be removed if you're confident the pagebreak
-%   problems won't occur.
+%  I've run into a situation where the index wants to start on the very
+%  last line of the page, and I actually get errors: ``Package multicol
+%  Error: Error saving partial page.'' The problem goes away if I fiddle
+%  with some lines so that the index starts elsewhere. Putting in a
+%  clearpage below makes the index start nicely in the middle of a page
+%  (until my change history gets too long!) and solves all those
+%  problems. It can be removed/pulled into this comment if you're
+%  confident the pagebreak problems won't occur.
+% \clearpage
 % \fi
-% \clearpage
+
          'sagetexpackage.ins',
          'sagetexpackage.pdf',
          'sagetexparse.py',
-         'sagetex.sty',
-         'README.spkg'])])
+         'sagetex.sty'])])
 
 
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.