Bug 150547 - RFE: Add a comment block for each of the included repo files.
Summary: RFE: Add a comment block for each of the included repo files.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-release
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Elliot Lee
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-08 05:15 UTC by Jef Spaleta
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-26 18:56:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jef Spaleta 2005-03-08 05:15:15 UTC
Description of problem:
In an effort to give as much information as possible to users of full
releases, i think it would be wise to have a comment block of text
describe what each included .repo file is. I think this is especially
important for fedora-devel.repo  and marginally important for
updates-testing.repo, which are not enabled by default.


A couple of sentences AND basic instructions on where to file bugs for
each repo.

For example  fedora-devel.repo:
[development]
#These packages are untested and still under development. This
#repository is used for updates to test releases
#This repository can see significant daily turn over and can see major
#functionality changes which cause unexpected problems with other
#development packages. Please use these packages if you want to work
#with the fedora Developers by testing these new development packages.
#
#fedora-test-list mailinglist is available as a discussion forum for
#testing and troubleshooting for development packages.
#
#Reportable issues should be filed at bugzilla.redhat.com
#Product: Fedora Core
#Version: devel
name=Fedora Core $releasever - Development Tree
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/development/$basearch/
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-rawhide
gpgcheck=1
enabled=0


And of course something similar for updates-testing.repo.  The idea
being give accurate information as to what the repo is used for, some
rational risk level assessment and where they should go for discussion
and bug reporting. 

-jef"i didnt even say 'eats babies' in my example text"spaleta

Comment 1 Elliot Lee 2005-04-26 18:56:36 UTC
I've stuck this text into the fedora-release module. If people write the actual
text for the other .repo files, I can either commit it or just give them direct
access to commit (if you join the 'cvsfedora' group in the account system,
you'll have commit access).


Note You need to log in before you can comment on or make changes to this bug.