Why is there a "logos" directory in the
? Shouldn't that be located in
it's used by configure before
has been established.
note that it would be better if they were svn links, rather than copies...
Can we use this to link to pattern skin css files, and perhaps TWikiDocGraphic icons?
We need to revisit this. The cgi-bin directory should only
contail cgi scripts. For example, the TWiki:Codev.TinyWeb
webserver treats all files below cgi-bin as cgi scripts, thus tries to execute
. How about placing the configure images relative to the bin, such as
, e.g. the TWiki pub dir?
As long as the dir is independent of the rest of the TWiki install and it can be found by configure.
You cannot guarantee that
is reachable using a relative path. That's the whole point of the
setting, isn't it?
You could move
the logos directory up a level (to the root) and require that it is always in that position relative to the scripts.
but the bin directory can be moved as well, so how to enforce the position?
We could add a new top level dir called
or the like and document to keep this at the same level as the bin dir in case the bin dir is moved out of the twiki tree. But then, this seems overkill.
Rethinking this, the TinyWeb is a special case, admins can still use the configure script with the current setup, they just do no see the images. Discarding.
(We need a nicer name than "discarding". Such as "Not suitable"?)