Runtime dependencies that are constant for all platforms are listed in
debian/control.{top,bottom}.in under the stanza for the related binary
package.Runtime dependences that vary from platform to platform and are not autodetected by dpkg-buildpackage are listed in debian/configure. Right now this is only @KERNEL_HEADERS@, so this variable would need to be renamed or a new variable would need to be created and substituted. Compile-time dependencies are handled similarly, but in the very top stanza of debian/control.top.in. Optional features that some users want to install and others do not are best implemented via multiple binary packages, particularly if a large amount of disk space is used by the optional feature's dependencies. Creating a new binary package involves making a new Package stanza in debian/control.bottom.in and a new list of files to include in that binary package in debian/<subpackagename>.files or .files.in if substitution of @-variables is required. Perhaps an appropriate package name would be linuxcnc-camview. Optional features that don't even exist on all supported platforms would be done similarly to how (in master branch), debian/configure decides whether to include e.g., debian/control.uspace-rtai.in in the generated debian/control file. Of course, src/configure.in and src/Makefile "make install" support are also needed to get things in the right place for dpkg-buildpackage, as well as for RIP users. Jeff ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
