Messages in this thread |  | | | Date | Wed, 01 Apr 2009 20:39:09 -0400 | | From | Jeff Garzik <> | | Subject | Re: [PATCHSET 0/8 version 4] exofs for kernel 2.6.30 |
| |
Boaz Harrosh wrote: > On 04/01/2009 12:23 PM, Jeff Garzik wrote: >> Boaz Harrosh wrote: >>> If anyone wants to actually run this code and test it >>> then please start reading at: >>> http://open-osd.org >>> You will need to checkout the out-of-tree git (below) for the user-mode utilities. >>> Also the exofs.txt file in patch 7/8 should help >> >> hum... trying to play with this. If you want exofs to go upstream, I >> think you should have a release tarball containing the user-mode utils >> posted somewhere. Would make life a lot easier, both on early adopters >> and also on distribution packagers. >> >> Jeff > > You are absolutely right, once 2.6.30 will be out there will not be a need > to compile Kernel modules. > > About the binary package. I must admit I'm a total novice. What do I need to do?
All you need on your end is a sane setup for installation, including building of shared libraries and installing necessary headers for userland programs.
Each individual distribution can easily package your exofs-utils into a deb or RPM.
Some of my projects have to do this. Here is one way, the highly standardized GNU autotools.
Take a look at autogen.sh, configure.ac, Makefile.am, include/Makefile.am and lib/Makefile.am from git://git.kernel.org/pub/scm/daemon/distsrv/chunkd.git
That demonstrates how to handle building and installing a shared library, header files and programs.
A lot of people dislike GNU autotools, but it's main benefit here is that Debian/Red Hat/Novell/Canonical/etc. are well-versed in creating .deb or .rpm from GNU autotools builds. It makes integration into a Linux distribution much easier.
> BTW: > Source tar balls are available from the gitweb GUI by pressing on the > "snapshot" link next to any commit. I should link to it from the WiKi
Oh yeah, I forgot about that.
Jeff
|  |