Many CGI scripts are like this: either installed systemwide or per-user (blogging packages, for example). Is there a good systematic way to do this? Ideally the user would just make install and it would Just Work, but there probably needs to be some sort of decision, either presented to the user or in the make arguments, as to where the files are to be installed.
In reply to Best practices for packaging CGI scripts by ajkessel
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |