Adding URLs to package build process

[Paul Kienzle]

There are a number of packages out on the net which are clearly 
intended to be used (otherwise they wouldn't be on the net in the first 
place) but don't have any stated license terms.  That means we cannot 
rehost them on octave-forge or include them in octave.  Authors of 
these packages frequently do not respond to requests for clarification.

Could the packaging system be extended so that it can download for 
URLs, apply a simple patch to add the normal packaging information, and 
build the resulting package?

        - Paul