Bug 179503

Summary:	"Documentation" package group needed in Anaconda
Product:	[Fedora] Fedora	Reporter:	Paul W. Frields <stickster>
Component:	comps	Assignee:	Tim Powers <timp>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://fedora.redhat.com/projects/docs/
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-25 00:26:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paul W. Frields 2006-01-31 21:52:03 UTC

*** NOTE:  Bug originally entered as HIGH priority as an attention-getting
strategy, and due to closing (but hopefully still slightly open) window of
opportunity.  This can be reclassified as ENHANCEMENT without hurting anyone's
feelings. ***

Description of problem:

The Fedora Documentation Project is ready to start packaging documentation for
FC5, hopefully in Extras by the time of FC5test3.  To make documentation
installation more seamless for the user, we'd like a group listed in anaconda
where the user can pick up the Yum Software Management Guide, Developers Guide,
etc., etc.  The documentation will automatically install via scrollkeeper and
various support files are deposited in correct places for GNOME yelp, KDE
khelpcenter, and the Main Menu.  (Eventually we may try to integrate with the
default Firefox installation, but for right now these were the targets we could
hit quickly and effectively.)

A name like "Official Documentation" might be good, although alternatives are
welcome.  If we can't hit this for FC5, if someone could comment to this bug
that would be helpful, so we can make other marketing plans, such as in the
release notes.

Comment 1 Jeremy Katz 2006-01-31 22:09:39 UTC

This is all handled by having packages with appropriate groupings in the comps
file.  anaconda doesn't have any hard coded idea of what the package groups are
(and shouldn't).

Comment 2 Paul W. Frields 2006-01-31 22:25:49 UTC

What do you say, comps maintainer(s)?  Reopening and reassigning there for input.

Comment 3 Jeremy Katz 2006-01-31 23:18:15 UTC

If the packages are in Extras, then they go in the Extras comps file.  There's
support for a comps file per repo and with that, things will Just Work (tm)

Comment 4 Jesse Keating 2006-02-25 00:26:39 UTC

The packages are in Extras, not Core, so the change has to go into Extras comps.
 Closing this bug as NOTABUG.