>I currently have a functioning usblib module, and for now it lives in >src/post_modules/USB in my personal tree. >I am now embarking onto creating a OneWire module/class which uses the >aforementioned USB lib to actually communicate with the 1-wire busmaster. > >The question is, where do I put all these modules. > >Most logical would be under a module named IO, so it would >become IO.USB.devices and IO.OneWire.devices or somesuch. >Then again, the USB module is completely written as a cmod. >The OneWire module might live as a Pike module.
Sounds good. >How do I solve the namespace problem, I'd like to unite them under master >module IO? The module build system actually supports installing modules in other places than the module root, it's just that most don't. Take a look at eg modules/Parser/configure.in. >Renaming the USB module to _USB, then inheriting the module under >lib/modules/IO.pmod again might work, but gets messy with autodoc, since >I'd like to keep the documentation in the cmod file itself. > >Any suggestions? >-- >Stephen.
