> Michael Watkins wrote:
>>Again, default path is different on other *nixes. /usr/local/bin/tidy in
>>the case of most (all?) BSDs.
>
> I think this one should be handled with a site config variable
> that gives the path to tidy, if you want to use it.
> I'll see how that works.

That sounds ideal. As would a list of config variables but grep works for
now.

> I think these are actually /www/python/bin/python in the distribution, and
> distutils modifies the !# line when you run the setup.py.
> I don't know the details.

This is a FreeBSD (perhaps *BSD) issue; I've never looked into distutils
to see where it derives paths

FreeBSD man page for hier
http://www.freebsd.org/cgi/man.cgi?query=hier&apropos=0&sektion=0&manpath=FreeBS
D+5.3-RELEASE&format=html

On FreeBSD the guts of Python and site-packages end up:
/usr/local/lib/python2.4

Binarys et al - not just python but most non-X packages added to the system:
/usr/local/bin

> Did you install, and *then* add the symlink in /usr/bin,

Yes.

Most installation or upgrade issues with Dulcinea are path related or
specific to the FreeBSD port of specific applications (only one that comes
to mind right now is Apache - IIRC Dulcinea expects apache.pid rather than
httpd.pid or something along those lines. Perhaps something else for the
config file... (and if it is already forgive me, haven't looked today).