On Sat, Dec 13, 2014 at 9:56 AM, David Evans wrote: > On 12/12/14 11:12 PM, Mojca Miklavec wrote: >> >> Assuming that all the working ports have been taken care of: what >> would you do with completely broken ports (that is: ports where >> p5.16-foo is just as broken as p5.20-foo)? Obviously we are not >> removing the existing broken variants. (I removed broken variants >> 5.8-5.14 in p5-wx for example, but there 5.16 worked just fine.) >> >> Mojca >> > If a port is completely broken and it's agreed that there is no hope of > fixing it, I would vote to remove it. > > p5-cgi-speedycgi may be such a port as it really does appear to be > completely broken and has not been updated since 2003. Ignoring the fact > that CGI in general is a bit outdated, there are other, perhaps better, ways > to accomplish similar goals (e.g. mod_fcgid, mod_fastcgi, mod_perl2). > > Dave
This particular port has apparently been broken for almost three years (at least for clang; maybe it still works on 10.6). It looks as if it was added as a dependency of another port (which switched to a different module by now). So yes, maybe it's just about time to remove this port. Mojca _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
