On Mon, Oct 27, 2008 at 08:33:37PM +0000, Amanda Waite wrote: > Nicolas Williams wrote: > >Do we really want cgi-fcgi in /usr/bin/? This sounds like something > >that belongs in /usr/lib. > > That's where it is on Ubuntu, OpenSUSE and Fedora. I know this is a bone > of contention, so I've gone for the "do what everyone else does" > approach. I doubt somehow that I'll be the one that decides where it goes.
That's likely good enough (see below) for me, but the materials have to stat this. > >Is there a *.pc file to go with this? > > > > What's a *.pc file? For a while stuff shipped scripts named <project>-config that would output things like the LDFLAGS and CFLAGS that you need to build using <project>. Then people switched to shipping /usr/lib/pkgconfig/<project>.pc which contains the same stuff. IF FastCGI does not include a .pc file, then I think putting cgi-fcgi in /usr/bin/ is a hold-your-nose-and-do-it kind of thing. But if it includes a .pc file then I'd rather move it to /usr/lib/ because the software that needs it will be able to find it by looking in the fastcgi.pc file at build time. > >s/At any point of time/At any point in time/ > > > >Who will deliver Perl/Ruby/Python/... language bindings for FastCGI? > > Those that own those particular components. I can speak for Ruby and > currently it will be installed as a Ruby Gem and given that Gem support > in Nevada and OpenSolaris is very robust these days we should be good to > go there. We are looking at ways of packaging popular gems but I'm not > going to commit to that until our team have got Ruby Gems updated to > 1.3.x. and I've finished my testing. OK, thanks.
