Archive for March, 2008

GoboLinux 014.01 released

Sunday, March 30th, 2008

The first ever bugfix-only release of the distribution is out now. The ISO is available from http://gobo.calica.com/gobolinux-iso/GoboLinux-014.01-i686.iso or http://kundor.org/gobo/iso/GoboLinux-014.01-i686.iso (MD5 c4c4827d8bbaf724e0e28f8ead47e7da), and will be from the other standard mirrors as they update.

This release fixes all known bugs from 014 and should be the most stable release yet. Thanks to Carlo for all the work he put in, and everybody else who reported bugs, fixed bugs, backported fixes to bugs, or just provided moral support.

This release will be distributed on 4,000 CDs at the International Forum on Free Software (FISL) in Porto Alegre, Brazil; if you’re not going to be there, download and give it a whirl.

Comments feed

Friday, March 21st, 2008

There’s now an Atom feed for comments here. The old commentrss module I was using apparently hasn’t been updated for Drupal 6, and the lack of feed made me let a spam comment sit there for over a week, so I decided to kill two birds with one stone and create a comment feed module for version 6 and also move it over to Atom while I was at it.

The feed is available at /atom/comments for anybody interested (probably only me), and if anybody wants to take a chance on the module it’s available here as well. It may end up on drupal.org at some point, but we’ll see how that goes.

More Bazaar in the tools

Thursday, March 13th, 2008

To follow up on adding support for GNU Bazaar in Compile, I’ve also added it to MakeRecipe in the same manner as the others.

I’ve also set up a few branches mirroring the Subversion tree – at the moment, only for Scripts, Compile, and Freshen, but others may follow if anybody else is using them. I’ve found them useful to split pieces of work across locations and to have decent branching to work with when adding features. The three branches up so far are at:

They’re kept up-to-date with bzr-svn (which was a bit of a pain to get going on Dreamhost; I had to compile half a toolchain in the process), and updated every half hour. Probably nobody else will be using them, but they’re there if somebody wants.

I think that’s the last of the work integrating bzr with the tools, so it should be all there for the next release of the tools, so I’ll move the branch recipes over from the experimental recipes repository into the mainline when that happens.

Bazaar support for Compile

Sunday, March 9th, 2008

I’ve added support for bzr-based recipes to Compile, in the same manner as SVN or git snapshots work. It was surprisingly simple to do once I got to work on it. Recipes specify the branch URL with bzr=http://…, the same as for the others, and it works pretty smoothly from there.

We’re in a code freeze right now for the move to SVN, so I haven’t checked it in, but I’ve posted a patch for anybody interested – sudo patch -p0 ~/Compile-bzr-support.patch in your /P/Compile/Current directory will add it to your install.

That will allow me to add recipes for more Bazaar plugins, that are often only released as public branches. They’ll live in the experimental recipes repository until there’s a Compile release with this in it.

Experimental recipes repository

Sunday, March 9th, 2008

I’ve set up a repository for experimental recipes I’ve written, such as CVS or SVN versions or major new releases, that aren’t necessarily fully reliable yet. At the moment, there’s an SVN trunk version of Subversion and a BZR-SVN recipe that depends upon it. There will likely be others in future. If you want to enable this repository for your own use, update /System/Settings/Compile/Compile.conf to add “http://mwh.geek.nz/files/gobo/recipes/experimental/” in the getRecipeStores array:
getRecipeStores=(
“http://gobolinux.org/recipe-store”
“http://mwh.geek.nz/files/gobo/recipes/experimental/”
)

The Subversion recipe particularly may not work, since it pulls directly from their trunk and could break at any time.

I would like to see these sorts of external repositories used for other unstable recipes as well – KDE 4, in particular, really shouldn’t be in the master store, so all of those recipes should go elsewhere. Those who wanted to use them could opt in by adding the repository to their Compile.conf