Jonathan Nieder <[email protected]> writes: > One possible answer to these questions is: "no, there is no standardized > configuration mechanism --- httpd-fcgi just means that the server allows > running FastCGI apps by some means documented at /usr/share/doc/<server > package name>/README.fastcgi, and some webapps will have their own > README.fastcgi instead of setting anything up automatically". That > would be fine --- I do not mean to suggest we should standardize on > anything more if that's all there is.
Well, "fine" in some sense (we have a few things like that now), but definitely less than ideal, and I'd rather not introduce a new case like that. One of the points of Debian Policy, and Debian packaging in general, is to integrate things. I really hate to see us throw up our hands and say "the end-user has to integrate it themselves." I'm wholeheartedly in favor of adding these new virtual packages, but I do think we should take the opportunity to specify an interface that providers of that virtual package implement, and that FastCGI scripts (and the other cases listed) can depend on. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
