I strongly support the idea of separate development packages over monolithic packages, even though you can sometimes find yourself missing the development package for something, a simple change to how the installer works with package management will make the situation no different than it would be with monolithic packages (from the end-user perspective):
If the Haiku development package is installed, development packages should be pulled in by default for any package for which they are available - if the package is installed after the initial installation, the option should be available to download the development packages from the depot - probably would be best to create the aforementioned meta development package which will pull in the most common of said packages.
The how-to for beginning Haiku development would be simple: 1. Make sure you have the Haiku Development package installed. 2. Develop. 3. Create a package. 4. Publish.As for the package creation, I'd think a package creator program could use one simple template to create multiple packages - just flag the included resources with an intended output package (, (pkg, -devel, -doc, -addons, -support, -pro, -lite, etc...).
The package relationships would be sorted so you could charge for some, give others for free, recommend some, or what-have-ya.
--The loon
