Thomas Arendsen Hein wrote:
> The fcgi script itself has the line "from flup.server.fcgi import WSGIServer",
> but maybe it could be added at the top of that file that something
> else is needed.
>
> README.Debian would be the second best choice.
Debian users generally look at README.Debian before the source file itself.
But the best would be to put the info in both.
> Ideally I'd like to see a "mercurial-fcgi" Debian package which
> depends on a compatible web server, python-flup and contains some
> documentation about how to get up and running.
Good idea. I think "apache2 | httpd, python-flup" would be good start
for dependencies. If some are missed, please tell me.
> (similar things could be done e.g. for the hgk extension, a package
> that enables the extension in e.g. /etc/mercurial/hgrc.d/hgk.rc and
> depends on tcl/tk)
Right. This would solve the problems with Recommends or Suggests or
Depends...
Note: William Pitcock had answered to my call on debian-devel and proposed
to co-maintain the mercurial package. So I hope that we will more reactive
on this package.
Best regards,
Vincent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
