Slashdot Mirror
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."
... remove the port if I have it installed, since my post Nov 7 cvsup will remove the port from my ports directory?
10b||~10b -- aah, what a question!
No, it's Firebird the database that is so insignificant it's been broken in ports forever and nobody noticed. Not Firebird the most kickass and bestest browser ever and stuff.
For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
Its not *BSD that is dying, but rather, just some of the ports that are dying. Whew, I was afraid for a while there I might have to move to a different OS.
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?
If a port is important to you, then fix it! Many of these ports only require trivial changes. So far today, I've submitted fixes for two of the ports that I want to live: games/xpuyo and emulators/its. Both only required simple changes.
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!
Now, if someone could just convice SourceForge to do the same.
To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
I disagree, at least in part. I saw some software in there that I had manually installed and didn't realize was in ports. I saw some stuff that I use but rarely update.
Also, just because a port is marked as broken doesn't mean no one has made an effort. There may be outstanding dialog with the developers or maintainers, and it hasn't produced a fix yet.
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