Broken FreeBSD Ports Scheduled for Removal
Dan writes "FreeBSD's Kris Kennaway says that the following FreeBSD ports are scheduled for removal on November 7 if they are still broken at that time and no PRs have been submitted to fix them. If you are interested in saving these ports, please send your patches to the maintainer. If the maintainer is unresponsive or the port has no maintainer, then please submit them via send-pr."
No. If you've already installed the port, then this change will not delete the installed copy. (It will still be deleted from your ports directory.) However, you may want to fix the port so it stays in the tree, if the port is important to you. Some of the so-called "broken" ports work fine, and some only need minor tweaking.
With the work going on with Freebsd/Gentoo/Fink/Darwin to work on a combined port system, I'm wondering if there is a automated ports checker to verify which ports compile out of the box? Seems there is alot of work that needs to be done to weed out the broken ports, and report ports with compile errors.
Also, a while back there was an OpenBSD announcement that the ports collection for both Open and Free had almost 20% ports that where broken. This small list is what, 3%? (guess)
Nice to see them to work on cleaning some ports, but is there a grand plan?
It sounds like you're describing bento, which Kris linked to in his email. If you ever wonder how a port build fails, or what it logs when it works, check bento!
I'm wondering if there is a automated ports checker to verify which ports compile out of the box?
/usr/ports and does a ``make index''. The ports that this fails on are most likely those listed. So, it's not automated but pretty good just the same.
I can't answer this fully but I know that Kris Kennaway posts ``INDEX build failed'' messages to the freebsd-ports mailing list quite frequently. From what I understand he goes to