FreeBSD woes.
I've been running FreeBSD on a laptop at work. Couple days ago I installed cadaver out of ports, and in the process it upgraded expat. X promptly stopped working. So I ran
portupgrade -rf textproc/expat2
and it compiled away for a full day.
Then X worked, but the UI widgets had no text. None. Menus. Toolbars. Window decks. Anywhere. Whee. Apparently gtk had failed to upgrade due to a lack of the XML::Parser
module. So I installed that and figured I better upgrade gtk20, so I'm running
portupgrade -rf x11-toolkits/gtk20
And it's still compiling now. I like FreeBSD a lot, but man, I've been compiling for about 3 days now (nights off.)
Cool. Now libxslt is failing on the version of libxml that's installed. I realize I've probably done something entirely clueless here, but linux is looking better and better here to me. It at least occasionally lets me use the machine.
UPDATE: From the FreeBSD GNOME Project: GNOME 2.6 Upgrading FAQ
NOTE: Do not run portupgrade(1) to upgrade to GNOME 2.6!
The simple answer is this:
CVSup your ports tree.
Download the FreeBSD GNOME Project's upgrade script.
Run the script as root. Read a good-sized book.
One last update: Ran the script yesterday am. It had me fix a few anamolies in the pkg database and then told me that it was about to rebuild all Gnome apps and dependencies, and that if I'd been "planning a long day trip, it might be a good day to take it." Yipes. I started the script at 10. When I left the office at 6, it was still compiling Mozilla.
OK, really the last: I came in this am and it worked, is done, and X has text. Yay.
Comments
Yeah, that's pretty much how I remember FreeBSD. I still have some fond memories of it but things like it taking forever to compile GUI toolkits are all too familiar.
Been a few years though.
Posted by: Ed Heil | May 25, 2004 6:35 PM