Thanks to the work of the bsd-sharp team, mono was updated to 2.0.1 this morning. Get it while it’s hot!
blogs.freebsdish.org updated to WordPress-MU 2.7
Apparently I missed the release last week, but it happened finally. I’ll send-pr the update for the port later.
If you encounter any issue, would like a new theme or plugin, leave a comment or drop me an email.
X.org 7.4 merged in the ports tree
There. Hopefully the upgrade should be a breeze. As usual, report problems on freebsd-x11@.
Enjoy!
FreeBSD Mono mailing list inauguration
I dropped an email to postmaster@ yesterday to get the freebsd-mono@ mailing list created and David Wolfskill created it today. Time to subscribe now!
End of X.org exp-run, starting mono exp-run
I think I’ve fixed everything there was to fix to merge X.org 7.4 in the tree. Except open-motif, which means 300+ ports are in duds right now. Open-motif is quite old in the ports tree (2.2.x) and requires Xprint, which I have removed. The update to 2.3.x is ready but I still need to bump PORTREVISION on ports that depend on it and fix what breaks.
In the meantime, I’ve started the mono experimental run. I don’t expect much fallout so it’s highly likely to hit the tree before X.org.
Waiting for new mono, here’s a new banshee
Banshee 1.4.2 was released yesterday. It comes with a handful of fixes. I don’t get the startup-at-freeze bug anymore, which is cool since it’s basically the only one I’ve encountered so far.
A few people have been working behind the scenes on FreeBSD/Mono for some time now. Wesley Shields (wxs@) sent a patch an hour ago which I’ll run through pointyhat once my X.org exp-run #3 finishes.
Hopefully mono 2.0.1 (I’ve been told 2.2 is in the works) should enter ports soon enough (along with a few ports updates). Stay tuned!
Xorg 7.4 experimental build has started
Well it took some time, but I’m finally running my first exp-run and it happens to be for xorg 7.4.
If everything goes according to plan, it should be ready some time this weekend, or early next week. I’m sorry it took so long it’s happening finally. We’ll probably be committing updates as the individual tarballs are released in the future, rather than waiting for katamari releases. Stay tuned.
Waiting for WordPress-MU 2.7
With WordPress 2.7 out of the door for a few weeks now, I’m eagerly expecting the release of WordPress-MU 2.7 now. So far I’ve been quite happy with 2.7 running on my personal blogs.
Anyway, in the meantime I’ve been installing more plugins, updating existing ones and also replacing some (both on my blogs and blogs.freebsdish.org). If you’re happen to have a blog there, here are the changes:
- New: Google Analytics
- New: WordPress.com statistics (you’ll need a WordPress API to use it, just go to WordPress.com and signup for an account, no need for the blog)
- New: NextGen Gallery (which actually won’t work, but it will with 2.7)
- Updated: OpenID
If you would like more themes and/or plugins to be installed, just let me know in the comments.
No such thing as bad publicity
I’m only two drinks away from installing Microsoft Bob.
ReviewBoard Install
Following Christian Hammond’s last post about ReviewBoard, I figured I would give ReviewBoard a try. Basically, it’s a good solution if you’re using any kind of pastebin website to share patches and get people to review it. It has syntax highlighting, a pretty good diff viewer. You can alter the patches and add comments,... It’s still a beta so expect rough edges, but it’s really neat. It’s not really a replacement for a bugtracker, but it completes it quite well IMHO.
I’ve created an account for each developer, following the model forums.freebsd.org is using (‘@’ as a suffix). There doesn’t seem to be a way to reset a lost password, so I have to choose between setting a default password for everybody, asking interested people to mail me a password hash (algo$salt$hash, e.g. sha1$$<hash>, django supports a few algorithms), or just delete all the accounts and let people register themselves (I would just need to promote them with a ‘@’ afterwards).
Oh yeah, it’s happening here. Feel free to send bug reports upstream (when appropriate).
Comments? Suggestions?
Recent Comments