Make better use of Yocto packaging #33
Description
Current Behavior
Currently we are packaging code into just "native" and "target" packages. These packages contain binaries and supporting files, but no source code. We are also not packaging documentation. We are packaging build tools with the target package, even though they are needed in the native package as well.
Expected Behavior
Packaging should be cleaner and follow Yocto best-practices.
Context / environment
I am trying to make the EPICS packaging cleaner. I want to be able to package the source into the image so that we can re-build IOCs on-target if required; this would be really convenient for quick configuration changes (like dead camera swaps, add one more analog input channel, etc).
Suggested Solution
Take advantage of the default packages that are available: https://docs.yoctoproject.org/dev/ref-manual/variables.html#term-PACKAGES
${PN}-src ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc ${PN}-locale ${PACKAGE_BEFORE_PN} ${PN}
Source code/docs can be added to ${PN}-src and ${PN}-doc, respectively. A separate ${PN}-tools package could be added to ${PACKAGE_BEFORE_PN} and used to install any necessary perl, bash, etc that are needed across multiple packages. The dependent packages can DEPEND and RDEPEND on the ${PN}-tools package as necessary.