build: add tags for packaging - #172
Conversation
390c43a to
4c6868d
Compare
|
The Most package-build infrastructure should be able to specify what upstream-package-installed binaries actually get included into the distribution package, so what do the tags give us above that? Also, this will require a bump to the minimum meson version, I think. |
It simplifies the installation process for package-build infrastructure. Yocto and Buildroot for example have specific Meson integrations that automatically install binaries tagged with This project is broadly the mctp utils, mctpd, and the debug tools. The different groups don't depend on each other and any combination of them might be wanted, so I thought tagging them that way would be helpful. It also helps anyone who wants to automatically install a subset of the binaries.
I agree, installation tags were added in 0.60.0, so the minimum version would need bumping. |
Add tags to mctp utilities, mctpd, and debug tools to allow packagers to easily select features. Tag debug tools as installable to allow them to be installed when needed by packagers. Bump minimum meson version to allow tagging. Signed-off-by: James Lee <james@codeconstruct.com.au>
4c6868d to
d13a7c3
Compare
|
Added the meson version bump to the PR |
Add tags to mctp utilities, mctpd, and debug tools to allow packagers to easily select features. Tag debug tools as installable to allow them to be installed when needed by packagers.