Description of problem: Beaker currently relies on the 'beaker' subpackage to provide modules that can be used by all the sub-packages. The problem (well, the main one) is that an accurate description of the current 'beaker' package provided by Summary, does not describe Beaker overall. This is a problem because that same Summary is used in places (i.e certain build systems) that attempt to give a Summary of Beaker. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Build Beaker 2. Look at the summary of the package provided by the build system 3. Actual results: Describes Beaker as a "File system layout for Beaker" Expected results: Something more applicable to what Beaker actually is/does Additional info: It's been decided that we should move the current content of the 'beaker' sub-package into a 'beaker-common' sub-package. That leaves us free to describe Beaker in the outer most Summary without also trying todescribe the contents of a specific sub-package
The problem is that the RPM applies the same Summary to the SRPM and the base RPM. Switching to a more conventional subpackage of -common for common stuff (with no base package) will let us set the SRPM Summary and the -common subpackage Summary separately, so that they can both be accurate.
My current preferred overall summary is the one from the top of the capabilities page in the architecture guide: "Beaker is a full stack software and hardware integration testing system, with the ability to manage a globally distributed network of test labs." (from http://beaker-project.org/docs/architecture-guide/capabilities.html)
http://gerrit.beaker-project.org/#/c/3027
Beaker 0.17.0 has been released.