The conditions of a package for TeX Live can be found at this page:
TeX Live package contributions
I will quote some of the page to discuss the conditions.
Disclaimer: I am not part of the TeX Live team. This is just my way to see the licensing conditions and my interpretation might not be correct.
Questions can be asked in the TeX Live mailing list (...
You can't use tlmgr (or its front-end TeX Live Utility). There is a script called getnonfreefonts at http://www.tug.org/fonts/getnonfreefonts/ that you have to download with the Terminal command
curl -O http://tug.org/fonts/getnonfreefonts/install-getnonfreefonts
and then install with
sudo texlua install-getnonfreefonts
Then you can get direction on its ...
Regarding flat .zip vs. .tds.zip, CTAN now rejects uploads that consist only of a TDS-structure, whether as a .zip or not. They now require creating a "browsing-friendly" relatively flat structure for the main tree.
Regarding creation of .tds.zip, I would strongly discourage doing it here. And in general, unless there is a specific reason to do so. ...
Whether such an update is allowed at all depends entirely on the licence/copyright conditions under which the original code was distributed. If it is LPPL version 1.3 there are explicit conditions under which maintenance may be taken over. Similarly if it is GPL then in place edits are not blocked by the licence. But in general, unless such a licence has ...
Not all LaTeX packages have a dedicated TeX Live package for them. In particular, several small packages by Donald Arsenau are grouped together in a genmisc package. So
sudo tlmgr install genmisc
should solve the problem.
You can see it in the CTAN page: http://ctan.org/pkg/nth
Generally I recommend installing a full TeX Live and forget about hunting for ...
Edit: The code is now hosted on Github.
Thanks to Ulrike, who pointed out existence of the xml interface on CTAN, I was able to create simple and dumb lua script, using wget command and my luaxml package.
The idea is that you pass the package name as argument for this script and biblatex entry is printed on the standard output. First whole script, ctanbib....
Great, I should be sleeping by now, but no, I had to code something! :) Somebody please call the authorities.
Here goes my pathetic attempt to provide the raw data you want. Since I had no idea of a good name (namely bird names, of course), I wrote a small application called ctaninfo. Here it comes:
paulo@alexandria ~$ java -jar ctaninfo.jar
And then we ...
Your question is a good one, but reveals one of the fundamental flaws in the way Linux-like (and I include here MacPorts) package management systems work when it comes to TeX distributions. The problem is that packages (in the TeX sense) are qualitatively different from packages in the Linux sense, but the Linux packagers don't seem to recognize the ...
Congratulations for your new package and thank you for taking your time for the documentation too.
For the packages to reach to the widest audience and to be able to be updated in a structured way via various update mechanisms, CTAN is the standard medium to upload a package.
As Joseph Wright commented, see
How to upload my packages or document classes ...
I don't think that there is a single best practice --- it partly depends in what way your package has become obsolete.
One of the strong goals of LaTeX is continued backward compatibility, i.e., the ability to reprocess old documents successfully even after a long period of time and in fact that is something tat most of the time works surprisingly well (e.g....
The 31st of October is the day of a festival called Halloween. This custom was established long time ago to scare away ghosts by dressing up as spooky creatures oneself. It is common to decorate your house with horrifying accessories and since CTAN is the home of TeX it is all Halloween-themed today.
Draw a turkey, a pumpkin ...
That is not CTAN and the pdf copy is illegal. As Knuth says on his webpage
The source file texbook.tex for The TeXbook has been available for
many years, and it begins with the following lines:
% This manual is copyright (C) 1984 by the American Mathematical Society.
% All rights are reserved!
% The file is distributed only for people to ...
There are at least four ways to find the documentation of a package or class.
Both TeXLive and MikTeX provide the texdoc command line tool which will usually find the correct documentation for a package with the following command:
For example, to find the TikZ (or pgf) manual you can just type:
If that ...
As Joseph writes build.lua and makefiles are for the development and not for CTAN (and I just removed the makefiles from the luaotfload upload for this reason). They can contain code and settings which are not suitable for a normal user installation like the call to local tools, or specific locations.
As an example in the build.lua of the lualibs package ...
There is nothing to stop you including build scripts in CTAN uploads: for example, in the past beamer used to have the Makefile on CTAN. However, a build script is not part of the package itself:, but is rather a convenience for the developer. (In the end, one can always extract a package and create documentation by hand.) Most notably, it's not usual to ...
TeX Live 2012 (2012-09-19)
$ egrep -c '\.sty$' ls-R
$ egrep -c '\.cls$' ls-R
$ egrep -c '\.(sty|cls)$' texmf-dist/ls-R
Windows has findstr, but it has some limitations. For example, it cannot detect Unix line ends or the end of the last line, if the file does not end with a end-of-line marker.
The equivalent for wc -l is find /c /v ...
I'm writing this answer as requested in the comments to the question, incorporating some of Bruno Le Floch's ideas. Since I know nothing about KML syntax, suggestions in this regard are very welcome!
Maintaining TeX-specific versions of the datasets is likely to produce a less than ideal solution. First, it is inefficient since it will need to duplicate ...
If you are using TeXLive, tlmgr can backup installed versions (it already does this automagically) and restore previously installed; see its documentation. I don't know if MikTeX offers something similar. And the mercurial repository of CTAN offers older versions - but you'll have to install them manually.
If you use tlmgr, you can run tlmgr restore [pkg] ...
CTAN .. doesn't provide any guidance on quality
I happen to have reflected on this question. :-)
The packages that have repeated functionality is not a large percentage of the archive as a whole, but for jobs that people often want to do you do see redundancy. We can imagine a number of attacks on that issue.
For instance, CTAN could track downloads and ...
If a package is unmaintained, CTAN will allow you provide an update, perhaps also taking over maintenance. What is important, though, is to show that this is the case. What CTAN are very keen to avoid is multiple people trying to change the same package.
It is worth noting is that a maintainer may decide not to change code: stability can trump bug fixes. ...
Most l3build scripts are somewhat tied to the test framework and usually test files are not shipped to ctan. Anyone who wants to install via l3build would most likely be better served by getting from a source repository such as GitHub rather than ctan. "waiting" for a ctan upload to reach texlive is usually only a day or so, so basically no one should be ...
So that this question gets an answer, here's a summary of the comments. To answer your specific questions:
It's perfectly fine to put non-TeX but TeX-related software on CTAN. This sort of thing is found in the support directory of CTAN.
It is also quite fine to upload compiled binaries to CTAN, as evidenced by the existing binaries in the support ...
there is a read-only copy of the
catalogue source, omitting author details at rsync://rsync.tex.ac.uk for use with rsync. (the author details contain email addresses, so we decided simply to omit them. for the same reason, we can't simply publish our svn pointer -- that remains protected.)
the copy is updated daily.
(nb, i tried to use the facilities ...
Ultimately, this is up to you as the developer. Normally, I would suggest that for a new package you put sufficient detail for someone to understand what it does, much like an abstract.
Package foo provides support for [some specialist area]. It makes
available [some interfaces] which are useful because ...
For updates, I favour having a simple bullet ...