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."
I noticed that they are removing Firebird ! Shouldn't they give the mozilla team a bit more time to stabilize it ? It just came out.
Why are they removing Java???
... 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!
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.
At some point, you just have to cut the fat. If these ports have been broken for so long and no one has made an effort, then their disappearance should be transparent. In fact, I would like to see this logic applied to the entire PR system. Old PR's should be closed and archived as "known issues."
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!
have you tried 4.8? how does that work? Have you tried NOT installing the ports at first and putting them in later?
*BSD dies at the end of Matrix Revolutions
Hey, I think they left lang/perl off by :)
mistake.
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
Please, an experienced coder needs to fix dcgui, for the sake of the RIAA.
"The lesson to be learned is not to take the comments on slashdot too literally." --Vinnie Falco, BearShare
The news of freebsd hitting 9000 ports hasn't gone old when they already admit that the figure was inflated by including defunct software? :-)
0.2.9 is out?
:)
I've been running 0.2.16 for a few months!
iqu
Anyway, maybe it works under 4.7, or 4.8, (though I wouldn't know...) but it doesn't work for me on 5.1
-Tim
-Tim