Date: 26 Jul 2005 17:10:44 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: freebsd-questions@freebsd.org Subject: Re: fastcgi port fixed but not updated? Message-ID: <44zms9mfxn.fsf@be-well.ilk.org> In-Reply-To: <20050726103124.S67832@malcolm.berkeley.edu> References: <20050726103124.S67832@malcolm.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Friedman <mikef@ack.Berkeley.EDU> writes: > I've recently discovered a problem report for the mod_fastcgi (2.4.2) > port: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/79774. The > report seems to indicate that the port was fixed shortly after the PR > was sent (May 31), yet I just did a cvsup and the buggy port still > shows up. > > I have made the fix to my copy of the port and it does work, but why > isn't the fixed version available via cvsup? My cvsup log (run just > this morning) shows that the fastcgi Makefile was checked out, yet its > date is still early on May 31, apparently just before the fix was > done, according to the PR. > > Anyone know what might be going on? Since the fastcgi port is called > by the rt-3.4.2 port (which is my real interest), keeping my fixed > version of the former around under a different name is not really a > good option, in case I need to update RT. The bug report claims that the install fails. It works fine for me with the Apache 1.3 port, so I suspect that a more sophisticated fix would be needed; if the path were hardcoded as you suggest, the port would *only* work with Apache2.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44zms9mfxn.fsf>