Those packages all depend on libow, so that could be it's own package. In fact, the dependencies are:
libow (called owlib in the source code) <- libusb (?libpthreads) owfs <- libow (and fuse) owhttpd <- libow owftpd <- libow owserver <- libow owcapi <- libow owperl <- libow (and swig for building) owphp <- libow (and swig for building) owpython <- libow (and swig for building) owtcl <- owcapi owdir <- none owread <- none owwrite <- none And all the ownet modules have no dependencies I believe. Paul Alfille On Sun, Aug 22, 2010 at 11:15 PM, Joshua J. Kugler <[email protected]>wrote: > Better idea: for the Python, Perl, PHP, and Tcl modules, break them out > into separate modules such as: > > owfs (main module) > owfs-python > owfs-php > owfs-perl > owfs-tcl > > And the like. You might even take a look at the feasibility of break > out the capi into its own module, as well as some of the others. That > way, you don't have to install what you don't want/need. > > j > >
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
