Bug 1072143

Summary:	common code should be packaged in a beaker-common subpackage, not the base package
Product:	[Retired] Beaker	Reporter:	Raymond Mancy <rmancy>
Component:	general	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.15	CC:	aigao, asaha, dcallagh, ebaak, rmancy, tools-bugs, xma
Target Milestone:	0.17
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-10 23:27:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raymond Mancy 2014-03-04 03:37:10 UTC

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

Comment 1 Dan Callaghan 2014-03-04 03:42:16 UTC

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.

Comment 3 Nick Coghlan 2014-03-04 03:50:47 UTC

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)

Comment 4 Amit Saha 2014-04-23 02:50:23 UTC

http://gerrit.beaker-project.org/#/c/3027

Comment 7 Dan Callaghan 2014-06-10 23:27:57 UTC

Beaker 0.17.0 has been released.