installpkg_remote  v. 0.3
upgradepkg_remote  v. 0.3
----------------------------------------------------------------------------
Note: You may need to change the permissions on these files in order to 
make them executable.  
	chmod 744 installpkg_remote
	chmod 744 upgradepkg_remote
----------------------------------------------------------------------------
installpkg_remote:

This is a modified version of the Slackware installpkg.  It is able to
fetch packages remotely via http or ftp, using wget.  Broken downloads will
be resumed where they left off if possible.

To install a package specify the full location of the package, e.g.:

  ftp://ftp.yourmirror.com/linux/slackware/slackware-8.1/slackware/ap/zsh-4.0.4-i386-1.tgz
 or
  http://yourmirror.com/linux/slackware/slackware-8.1/slackware/ap/zsh-4.0.4-i386-1.tgz

The script will then fetch your package to /var/tmp by default (this can be
changed through the DOWNLOAD_DIR environment variable).  It will then install 
the package as usual.  Of course, you can still install local packages as usual.

If you need to specify options to wget, you can add them to your
global /etc/wgetrc, or to the users $HOME/.wgetrc.  One common option
you may need is to use passive ftp.  This can be enabled by
"passive_ftp = on" in your wgetrc.

Implemented a -delete switch to delete the package after a remote install, e.g.:
  installpkg_remote -delete http://yourmirror/yourpackages-3.4.2-i386-3.tgz
-----------------------------------------------------------------------------

upgradepkg_remote:

This is a modified version of the Slackware upgradepkg.  It is able to upgrade 
packages remotely given that my modified installpkg script is also installed
(Since upgradepkg uses installpkg for its installs).  It will use the same
DOWNLOAD_DIR environment variable for setting the location to store downloaded
packages, and also use the same .wgetrc options.

In the 0.2 releases and above, you no longer need to replace your original Slackware
installpkg and upgradepkg scripts.  This is now a completely standalone project.
The only requirement is that your upgradepkg_remote and installpkg_remote scripts
be in the same directory, and named upgradepkg_remote and installpkg_remote as they
are by default.

This will work exactly the same as the original upgradepkg, except you now have the
option of giving a remote location of the new package, e.g.:
  upgradepkg ftp://ftp.yourmirror.com/slackware-8.1/package-4.2.3-i386-3.tgz
 or
  upgradepkg package-4.2.3-i386-2%ftp://ftp.yourmirror.com/slackware-8.1/package-4.2.3-i386-3.tgz

Implemented a --delete switch to delete the package after a remote install, e.g.:
  upgradepkg_remote --delete http://yourmirror/yourpackages-3.4.2-i386-3.tgz

READ BELOW for info on why one switch uses "-" and the other uses "--"
------------------------------------------------------------------------------
Known Issues:

1. DONE - As of now, packages are left on disk after they are downloaded.  Perhaps a switch
should be implemented to allow for removal of the .tgz after successful 
installation. 
	installpkg_remote -delete
	upgradepkg_remote --delete
	Notice how one is "-" and one is "--".  This was done to maintain the form of 
	  current switches in both of these scripts.  The installpkg script uses one dash
	  and the upgradepkg script uses two dashes for its switches.  Don't ask me why
	  why it was done this way, ask Pat :)  I'm just trying to keep things uniform
	  within each script.

2. FIXED - The upradepkg_remote script will download the package whether it is already 
installed or not.  If the same version is installed that you are trying to upgrade, it
doesn't make much sense to waste the bandwidth downloading the package. 


Please let me know if you find any bugs or have any comments/suggestions/ideas.

Matt Rickard
mjr318@psu.edu