[Slackbuilds-users] suggestion for READMEs

Erik Hanson erik at slackbuilds.org
Thu Oct 22 00:50:22 UTC 2015

On Wed, 21 Oct 2015 18:12:07 -0400
B Watson <yalhcru at gmail.com> wrote:

> graphics/paraview and academic/Xyce both have fancy "web 2.0" download
> pages, I don't seem to be able to download the sources with either
> wget or curl.

Those links should be fixed. Xyce is giving me 403 in a browser,
and paraview could follow the AUR link as an example.

> Maybe the maintainers of these packages could add a note to the
> READMEs, saying "sbopkg can't automatically download the source, it
> must be downloaded with a javascript-capable browser", something like
> that. Precedent for this would be the development/jdk README.

We already require direct download links, which I think implies an
ability to download via typical command line tools. There may be a few
exceptions, such as jdk (truecrypt was, at some point) but I think we'd
be better to not allow any more in the future.

> Maybe also would be a nice thing to add to the submitter guidelines at
> http://slackbuilds.org/guidelines/: "If the source can't be downloaded
> non-interactively (e.g. with wget), please make a note of this in your

The guidelines explicitly state "direct download link(s) ..."


More information about the SlackBuilds-users mailing list