Fixes to broken ports

[Kris Kennaway]

Hi guys,

As you probably noticed I have done a sweep through the ports tree and
marked BROKEN those ports that currently fail on both the 4.x and 5.0
package builds.  I tried not to mark BROKEN ports that fail due to a
spurious bento error, but it's possible that I might have overlooked
some: if so, I apologise - just let me know and I'll remove the BROKEN
tag if it was inappropriately added.

I didn't check for PRs containing fixes before committing - in fact I
know that a lot of the ports I marked BROKEN do have fixes in the PR
database.  Mark Linimon has been looking into compiling a list of PRs
that fix these ports.

This kind of thing is periodically necessary to clean up the ports
collection and improve the interface for the end-user: trying to build
a port only to discover that it fails with a mysterious error makes
FreeBSD look bad.  Also, by marking the port BROKEN it raises the
visibility of the problem, and it encourages committers and other port
users to investigate and fix the problem.  In fact, in the 48 hours
since I started this sweep, a number of ports broken for 6 months or
more have already been fixed.

If you're the maintainer of a port that was marked BROKEN, for which
you have already submitted a fix, please do not take offense to my
commit to your port.  You've done the right thing by pre-emptively
fixing the problems with your port, and it's our fault for not
committing your fix before now.  Just drop a note to ports@ mentioning
the PR number that contains the fix, and one of our committers will
commit the fix.

Thanks,

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20030507/6ed8a146/attachment.bin