[ moving to devel ]
begin Slava Pestov quotation:
> I believe #1 is the best idea -- it will be easy for me to implement,
> and will save disk space on your end. (Another means to save disk
> space would be for you to drop TGZ downloads. Almost no-one needs
the disk space is inconsequential as well as negligible.
$ du -Hs ~/webs/archives/plugins
that includes every plugin ever released on Plugin Central (more or
the one thing that is a little weird about option 1 is what to do with
external JAR files. should they be included in the source-only download?
if not, people who download only source from the web site will not be
able to compile without either downloading the binary package as well,
or hunting down the external JARs for oneself.
> I have attached a new plugins.dtd that adds a DOWNLOAD_SOURCE element
> to BRANCH. So the old DOWNLOAD element should point to the binary
> download, DOWNLOAD_SOURCE should point to the source-only download.
> If the user specifies to download source, both will be downloaded,
> otherwise only the binary.
i have added this to the script output, but i have not yet actually
created all the referenced files. the URLs will not work until i do.