casa-mp-base
Public
Source
xxxxxxxxxx--- NEWS.orig 2018-11-29 17:05:39.000000000 -0600+++ NEWS 2018-11-30 02:02:13.000000000 -0600 ** Compiles on pre-ANSI compilers.-** Global wgetrc now goes to /usr/local/etc (i.e. $sysconfdir).+** Global wgetrc now goes to @PREFIX@/etc (i.e. $sysconfdir). ** Lots of bugfixes. ** Fixed a long-standing bug, so that Wget now works over SLIP connections.-** You can have a system-wide wgetrc (/usr/local/lib/wgetrc by-default). Settings in $HOME/.wgetrc override the global ones, of-course :-)+** You can have a system-wide wgetrc (@PREFIX@/lib/wgetrc). Settings+in $HOME/.wgetrc override the global ones, of course :-) ** You can set up quota in .wgetrc to prevent sucking too much data. Try `quota = 5M' in .wgetrc (or quota = 100K if you want your--- README.orig 2015-11-09 09:24:06.000000000 -0600+++ README 2015-11-16 11:05:27.000000000 -0600 Most of the features are configurable, either through command-line options, or via initialization file .wgetrc. Wget allows you to-install a global startup file (/usr/local/etc/wgetrc by default) for-site settings.+install a global startup file (@PREFIX@/etc/wgetrc) for site settings. Wget works under almost all Unix variants in use today and, unlike many of its historical predecessors, is written entirely in C, thus--- doc/sample.wgetrc.orig 2015-11-09 09:24:06.000000000 -0600+++ doc/sample.wgetrc 2015-11-16 11:05:27.000000000 -0600 ## Or online here: ## https://www.gnu.org/software/wget/manual/wget.html#Startup-File ##-## Wget initialization file can reside in /usr/local/etc/wgetrc+## Wget initialization file can reside in @PREFIX@/etc/wgetrc ## (global, for all users) or $HOME/.wgetrc (for a single user). ## ## To use the settings in this file, you will have to uncomment them, ##-## Global settings (useful for setting up in /usr/local/etc/wgetrc).+## Global settings (useful for setting up in @PREFIX@/etc/wgetrc). ## Think well before you change them, since they may reduce wget's ## functionality, and make it behave contrary to the documentation: ##--- doc/wget.texi.orig 2018-11-13 08:54:31.000000000 -0600+++ doc/wget.texi 2018-11-30 02:02:13.000000000 -0600 Most of the features are fully configurable, either through command line options, or via the initialization file @file{.wgetrc} (@pxref{Startup File}). Wget allows you to define @dfn{global} startup files-(@file{/usr/local/etc/wgetrc} by default) for site settings. You can also+(@file{@PREFIX@/etc/wgetrc} by default) for site settings. You can also specify the location of a startup file with the --config option. To disable the reading of config files, use --no-config. If both --config and --no-config are given, --no-config is ignored. @ignore @c man begin FILES @table @samp-@item /usr/local/etc/wgetrc+@item @PREFIX@/etc/wgetrc Default location of the @dfn{global} startup file. @item .wgetrc @cindex location of wgetrc When initializing, Wget will look for a @dfn{global} startup file,-@file{/usr/local/etc/wgetrc} by default (or some prefix other than-@file{/usr/local}, if Wget was not installed there) and read commands-from there, if it exists.+@file{@PREFIX@/etc/wgetrc} and read commands from there, if it exists. Then it will look for the user's file. If the environmental variable @code{WGETRC} is set, Wget will try to load that file. Failing that, no The fact that user's settings are loaded after the system-wide ones means that in case of collision user's wgetrc @emph{overrides} the-system-wide wgetrc (in @file{/usr/local/etc/wgetrc} by default).