> So the aim is to have a mapping from sitekeys to actual project
> directories containing the generated HTML.
That's right.
> Ok. Am I correct in understanding that the actual system cgi script is
> not provided by global but it is to be created by the user or system
> administrator.
At first, you need to get the CGI scripts by executing htags, and copy
them to the system cgi area. It is required only once.
(The scripts above will become static files in the future.)
$ htags -f ... # in any place
# cp HTML/cgi-bin/*pl /usr/local/apache2/cgi-bin # required only once
#
# From now on, normal operation
#
$ cd usr/local/src/grep-2.9
$ gtags
$ htags -f --system-cgi=prj1 # 'prj1' is embeded in the form
$ cat /usr/local/var/gtags/sitekeys/prj1
/usr/local/src/grep-2.9/HTML
$ _
[CGI program]
+-----------------------------------------------
|if (key is embeded) {
| Get key => 'prj1'
| Read /usr/local/var/gtags/sitekeys/prj1
| => /usr/local/src/grep-2.9/HTML
| chdir /usr/local/src/grep-2.9/HTML
|}
|Do the job.
> I am looking to see if there's an obvious way to package this. I might
> resort to turning this feature off in the first update and then add it
> to the package as I understand better what is needed on the packaging
> side.
I agree. But I think it is no problem on as is basis, because the use
of this feature is very difficult. I am responsible about it.
It seems that you do not need to take responsibility for it.
Shigio
--
Shigio YAMAGUCHI <shi...@gnu.org>
PGP fingerprint: D1CB 0B89 B346 4AB6 5663 C4B6 3CA5 BBB3 57BE DDA3
