|
Get Bomns Via Source Tarball
There are several ways to get your hands on Bomn for Linux, but the most common is probably to grab a
source tarball off the project page and compile it.
I don't currently provide any binary packages, because they are, in general, a pain in the ass to maintain. If anybody
wants to contribute binary packages for any BfL version, I would be glad to put them up.
Get the Latest Source Via CVS
For the people who want bleeding edge code, or a fix for a recently-found-but-not-in-latest-release-yet type bug,
there's always CVS. Of course it'll be less tested, and maybe less stable, but you always have the latest release
to fall back on. If you don't know how to use CVS, don't despair, it's
quite simple. First off, to check out a spanking fresh copy of the code, do:
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/greenridge login
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/greenridge co -P bomns
That'll start pulling down files like there's no tomorrow, and soon you'll have a shiny new "bomns" directory. Then just proceed
to install normally. After you've already done that once, luckily, you never have to do it again. The cool thing about CVS is
that it will be able to tell which files need to be updated and which don't. So instead of downloading an entire new release, you might
just download a few k of changes! Anyway, to accomplish this feat just cd into your bomns directory and type the following:
cvs login
cvs update -dP
That'll compare your local version of the Bomns for Linux code with the latest CVS, and do anything necessary. Simple.
NOTE: You can also browse the CVS repository, which
is cool.
|
|






|