Ahhh...
Links is not built 'on the fly' though, they are static pages. I suppose you could have nph-build create duplicates of everything, using different templates. Sounds a bit complicated...
I think you could have two (or more) full Links2 scripts, using different templates, but all using a common database. Only use one of the Links2 as your admin to add, etc, the others only to create different looks (skins). Still, a lot of work.
The changes to make would be at the bottom of links.cfg, where the paths to db files are found:
# Extra Paths -- unless you feel the need to rename files, you
# can leave this as is.
In the second bunch, change this:
$db_script_path
to:
$db_script_path2
then add this at the top of the file, after the original:
# PATH of Admin CGI directory. No Trailing Slash.
$db_script_path2 = "/alex/links/cgi-bin/admin";
where the path would point to the one install of links that you use to add links info.
# PATH and URL of Admin CGI directory. No Trailing Slash.
$db_script_path = "/cgi-bin/links/admin";
$db_dir_url = "
http://localhost/cgi-bin/links/admin";
# PATH of Admin2 CGI directory. No Trailing Slash.
$db_script_path2 = "/cgi-bin/links2/admin";
Leonard
aka PerlFlunkie