Commits

Anonymous committed 47b86c2

minor cleanups

  • Participants
  • Parent commits b72727f

Comments (0)

Files changed (2)

 pkg=sagetex
-dest=/home/drake/texmf/tex/latex/sagetex/
 dtxs=$(wildcard *.dtx)
 # the subdir stuff makes the tarball have the directory correct
 srcs=example.tex README sagetex.ins
 	/bin/bash -c "rm -f {$(pkg),example}.{glo,gls,aux,out,toc,dvi,pdf,ps,log,ilg,ind,idx,fdb_latexmk,sagetex.*}"
 	rm -f *_doctest.sage
 
-# make a tarball suitable for CTAN uploads, or for someone who knows how
-# to handle .dtx files
-ctandist: all
-	@echo
-	@echo Did you turn off Imagemagick in example.tex?
-	@echo
-	tar zcf sagetex.tar.gz --transform "s|^|sagetex/|" $(srcs) $(dtxs) example.pdf sagetex.pdf
-
 # otherwise, make gets confused since there's a file named "test"
 .PHONY: test
 test:

File py-and-sty.dtx

 %   |\newlabel{labelname}{{section number}{page number}}|
 % \end{center}
 % to the |.aux| file. When you use the |hyperref| package, there are
-% more fields in the second argument, but the first two are the same.
-% The |\ref| command just pulls in what's in the first field of the
-% second argument, so we can hijack this mechanism for our own nefarious
-% purposes. The function writes a |\newlabel| line with a label made
-% from a counter and the text from running Sage on |s|.
+% more fields in the second argument, but the first two fields are the
+% same. The |\ref| command just pulls in what's in the first field of
+% the second argument, so we can hijack this mechanism for our own
+% nefarious purposes. The function writes a |\newlabel| line with a
+% label made from a counter and the text from running Sage on |s|.
 %
 % We print out the line number so if something goes wrong, the user can
 % more easily track down the offending |\sage| command in the source