release-notes/devel Makefile, NONE, 1.1 README-en.xml, NONE, 1.1 about-fedora.menu, NONE, 1.1 about-fedora.omf, NONE, 1.1 about-fedora.xml, NONE, 1.1 about-gnome.desktop, NONE, 1.1 about-kde.desktop, NONE, 1.1 announcement-release.txt, NONE, 1.1 eula.py, NONE, 1.1 eula.txt, NONE, 1.1 fedora-devel.repo, NONE, 1.1 fedora-release-notes.spec, NONE, 1.1 fedora-release.spec, NONE, 1.1 fedora-updates-testing.repo, NONE, 1.1 fedora-updates.repo, NONE, 1.1 fedora.repo, NONE, 1.1 files-map.txt, NONE, 1.1 main.xsl, NONE, 1.1 readmes.xsl, NONE, 1.1 refactoring-notes.txt, NONE, 1.1 rpm-info.xml, NONE, 1.1 sources, NONE, 1.1

Paul W. Frields (pfrields) fedora-docs-commits at redhat.com
Tue Jun 27 21:54:37 UTC 2006


Author: pfrields

Update of /cvs/docs/release-notes/devel
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7999

Added Files:
	Makefile README-en.xml about-fedora.menu about-fedora.omf 
	about-fedora.xml about-gnome.desktop about-kde.desktop 
	announcement-release.txt eula.py eula.txt fedora-devel.repo 
	fedora-release-notes.spec fedora-release.spec 
	fedora-updates-testing.repo fedora-updates.repo fedora.repo 
	files-map.txt main.xsl readmes.xsl refactoring-notes.txt 
	rpm-info.xml sources 
Log Message:
Add content copied from FC-5 branch; this directory is where we will builg FC-6 release notes


--- NEW FILE Makefile ---
########################################################################
# Fedora Documentation Project Per-document Makefile
# License: GPL
# Copyright 2005,2006 Tommy Reynolds, MegaCoder.com
########################################################################
#
# Document-specific definitions.
#
DOCBASE        	= RELEASE-NOTES
PRI_LANG	= en_US
OTHERS		= #de it ja_JP pa pl pt_BR ru zh_CN 
FDPDIR		= $(PWD)/../..
########################################################################
# List each XML file of your document in the template below.  Append the 
# path to each file to the "XMLFILES-${1}" string.  Use a backslash if you
# need additional lines.  Here, we have one extra file "en/para.xml"; that
# gets written as "${1}/para.xml" because later, make(1) will need to compute
# the necesssary filenames.  Oh, do NOT include "fdp-info.xml" because that's
# a generated file and we already know about that one...

define XMLFILES_template

XMLFILES-$(1)=	$(1)/ArchSpecific.xml				\
			$(1)/ArchSpecificPPC.xml 			\
			$(1)/ArchSpecificx86_64.xml 		\
			$(1)/ArchSpecificx86.xml			\
			$(1)/BackwardsCompatibility.xml 		\
			$(1)/Colophon.xml				\
			$(1)/DatabaseServers.xml 			\
			$(1)/Desktop.xml 				\
			$(1)/DevelTools.xml 			\
			$(1)/DevelToolsGCC.xml 			\
			$(1)/Extras.xml 			\
			$(1)/Entertainment.xml 			\
			$(1)/Feedback.xml 				\
			$(1)/FileServers.xml	 		\
			$(1)/FileSystems.xml			\
			$(1)/I18n.xml				\
			$(1)/Installer.xml 			\
			$(1)/Java.xml				\
			$(1)/Kernel.xml				\
			$(1)/Legacy.xml				\
			$(1)/Multimedia.xml			\
			$(1)/Networking.xml			\
			$(1)/OverView.xml				\
			$(1)/PackageChanges.xml			\
			$(1)/PackageNotes.xml			\
			$(1)/Printing.xml				\
			$(1)/ProjectOverview.xml			\
			$(1)/RELEASE-NOTES.xml			\
			$(1)/Samba.xml				\
			$(1)/Security.xml				\
			$(1)/SecuritySELinux.xml			\
			$(1)/ServerTools.xml			\
			$(1)/SystemDaemons.xml			\
			$(1)/Virtualization.xml			\
			$(1)/WebServers.xml			\
			$(1)/Welcome.xml				\
			$(1)/Xorg.xml

endef

#
########################################################################
include ../../docs-common/Makefile.common
########################################################################
#
# If you want to add additional steps to any of the 
# targets defined in "Makefile.common", be sure to use
# a double-colon in your rule here.  For example, to 
# print the message "FINISHED AT LAST" after building 
# the HTML document version, uncomment the following 
# line:
#${DOCBASE}-en/index.html::
#	echo FINISHED AT LAST
########################################################################
define HACK_FDP_template
$(1)/fdp-info.xml::
	sed -i 's#legalnotice-opl#legalnotice-relnotes#g' $(1)/fdp-info.xml
endef

$(foreach LANG,${PRI_LANG} ${OTHERS},$(eval $(call HACK_FDP_template,${LANG})))


--- NEW FILE README-en.xml ---
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

<!ENTITY % ALPHA "IGNORE">
<!ENTITY % X86 "INCLUDE">
<!ENTITY % IA64 "IGNORE">
<!ENTITY % S390 "IGNORE">
<!ENTITY % HA "IGNORE">
<!ENTITY % X86-64 "IGNORE">

<!ENTITY RH "Red Hat"> <!-- The generic term "Red Hat" -->
<!ENTITY RHL "&RH; Linux"> <!-- The generic term "Red Hat Linux" -->
<!ENTITY FORMAL-RHI "&RH;, Inc."> <!-- Formal version -->
<!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
<!ENTITY PROJ "&NAME; Project"> <!-- The project's name -->
<!ENTITY DISTRO "&NAME; Core"> <!-- The software's name -->
<!ENTITY DISTROVER "5 test3"> <!-- The software's version -->

]>

<article id="index" lang="en" arch="x86;x86_64;ppc" os="test;final">
  <articleinfo>
    <title>&DISTRO; &DISTROVER; README</title>
    <copyright>
      <year>2006</year>
      <holder>&FORMAL-RHI;</holder>
    </copyright>
    <legalnotice id="legalnotice">
      <para>The contents of this CD-ROM are Copyright &copy; 2006 &PROJ; and
        others.  Refer to the End User License Agreement and individual
        copyright notices in each source package for distribution terms.</para>

      <para>&NAME;, &RH;, &RH; Network, the &RH; "Shadow Man" logo, RPM, Maximum
        RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover,
        RHmember, RHmember More, Rough Cuts, Rawhide and all &RH;-based
        trademarks and logos are trademarks or registered trademarks of
        &FORMAL-RHI; in the United States and other countries.</para>

      <para>Linux is a registered trademark of Linus Torvalds.</para>

      <para>Motif and UNIX are registered trademarks of The Open Group.</para>

      <para>Intel and Pentium are registered trademarks of Intel
        Corporation. Itanium and Celeron are trademarks of Intel
        Corporation.</para>

      <para>AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanced
        Micro Devices, Inc.</para>

      <para>Windows is a registered trademark of Microsoft Corporation.</para>

      <para>SSH and Secure Shell are trademarks of SSH Communications Security,
        Inc.</para>

      <para>FireWire is a trademark of Apple Computer Corporation.</para>

      <para>All other trademarks and copyrights referred to are the property of
        their respective owners.</para>

      <para>The GPG fingerprint of the <computeroutput>"Fedora Project
        &lt;fedora at redhat.com&gt;"</computeroutput> key is:</para>

      <para>CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2</para>
    </legalnotice>
  </articleinfo>

  <section id="dir-org">
    <title>DIRECTORY ORGANIZATION</title>

    <para>&DISTRO; is delivered on multiple CD-ROMs consisting of installation
      CD-ROMs and source code CD-ROMs.</para>

    <para>The first installation CD-ROM can be directly booted into the
      installation on most modern systems, and contains the following directory
      structure (where <filename>/mnt/cdrom</filename> is the mount point of the
      CD-ROM):</para>

    <screen arch="x86">
      <!-- <remark os="test">(x86)</remark> -->
<computeroutput>
/mnt/cdrom
  |----> Fedora
  |        |----> RPMS         -- binary packages
  |        `----> base         -- information on this release of Fedora
  |                               Core used by the installation process
  |----> images                -- boot and driver disk images
  |----> isolinux              -- files necessary to boot from CD-ROM
  |----> repodata              -- repository information used by the 
  |                               installation process
  |----> README                -- this file
  |----> RELEASE-NOTES         -- the latest information about this release
  |                               of Fedora Core
  `----> RPM-GPG-KEY           -- GPG signature for packages from Red Hat
</computeroutput>
    </screen>
<!-- repetitive for the moment
    <screen arch="x86_64">
      <remark os="test">(x86_64)</remark>
<computeroutput>
/mnt/cdrom
  |- - - -> Fedora
  |        |- - - -> RPMS         - - binary packages
  |        `- - - -> base         - - information on this release of Fedora
  |                               Core used by the installation process
  |- - - -> images                - - boot disk ISO image
  |- - - -> isolinux              - - files necessary to boot from CD-ROM
  |- - - -> README                - - this file
  |- - - -> RELEASE-NOTES         - - the latest information about this release
  |                               of Fedora Core
  `- - - -> RPM-GPG-KEY           - - GPG signature for packages from Red Hat
</computeroutput>
  </screen>
    -->
    <para>The remaining Installation CD-ROMs are similar to Installation CD-ROM
      1, except that only the <filename>Fedora</filename> subdirectory is
      present.</para>

    <para>The directory layout of each source code CD-ROM is as follows:</para>

    <screen>
<computeroutput>
/mnt/cdrom
  |----> SRPMS                 -- source packages
  `----> RPM-GPG-KEY           -- GPG signature for packages from Red Hat
</computeroutput>
    </screen>

    <para>If you are setting up an installation tree for NFS, FTP, or HTTP
      installations, you need to copy the <filename>RELEASE-NOTES</filename>
      files and all files from the <filename>Fedora</filename> directory on
      discs 1-5.  On Linux and Unix systems, the following process will properly
      configure the /target/directory on your server (repeat for each disc):</para>

    <orderedlist>
      <listitem>
        <para>Insert disc</para>
      </listitem>

      <listitem>
        <para><command>mount /mnt/cdrom</command></para>
      </listitem>

      <listitem>
        <para><command>cp -a /mnt/cdrom/Fedora
            /target/directory</command></para>
      </listitem>

      <listitem>
        <para><command>cp /mnt/cdrom/RELEASE-NOTES*
        /target/directory</command></para>
	<para><command>cp -a /mnt/cdrom/repodata
        /target/directory</command></para>
	<para>(Do this only for disc 1)</para>
      </listitem>

      <listitem>
        <para><command>umount /mnt/cdrom</command></para>
      </listitem>
    </orderedlist>
  </section>

  <section id="installing">
    <title>INSTALLING</title>

    <para>Many computers can now automatically boot from CD-ROMs. If you have
      such a machine (and it is properly configured) you can boot the &DISTRO;
      CD-ROM directly.  After booting, the &DISTRO; installation program will
      start, and you will be able to install your system from the CD-ROM.</para>

    <para arch="x86;x86_64"><!-- <remark os="test">(x86;x86_64)</remark> --> The
      <filename>images/</filename> directory contains the file
      <filename>boot.iso</filename>.  This file is an ISO image that can be used
      to boot the &DISTRO; installation program.  It is a handy way to start
      network-based installations without having to use multiple diskettes.  To
      use <filename>boot.iso</filename>, your computer must be able to boot from
      its CD-ROM drive, and its BIOS settings must be configured to do so.  You
      must then burn <filename>boot.iso</filename> onto a recordable/rewriteable
      CD-ROM.</para>

    <para arch="x86;x86_64"><!-- <remark os="test">(x86;x86_64)</remark> --> Another image
      file contained in the <filename>images/</filename> directory is
      <filename>diskboot.img</filename>.  This file is designed for use with USB
      pen drives (or other bootable media with a capacity larger than a diskette
      drive).  Use the <command>dd</command> command to write the image.</para>

    <note arch="x86;x86_64">

      <title>Note</title>
      <!-- <remark os="test">(x86;x86_64)</remark> -->

      <para>The ability to use this image file with a USB pen drive depends on
        the ability of your system's BIOS to boot from a USB device.</para>
        </note>
  </section>

  <section id="get-help">
    <title>GETTING HELP</title>

    <para>For those that have web access, see <ulink
        url="http://fedora.redhat.com">http://fedora.redhat.com</ulink>.  In
        particular, access to &PROJ; mailing lists can be found at:</para>

    <para><ulink
    url="https://listman.redhat.com/mailman/listinfo/">https://listman.redhat.com/mailman/listinfo/</ulink></para>

    <para>The complete &NAME; Installation Guide is available at <ulink
	url="http://fedora.redhat.com/docs/" />.</para>

  </section>

  <section id="export-ctl">
    <title>EXPORT CONTROL</title>

    <para>The communication or transfer of any information received with this
      product may be subject to specific government export approval.  User shall
      adhere to all applicable laws, regulations and rules relating to the
      export or re-export of technical data or products to any proscribed
      country listed in such applicable laws, regulations and rules unless
      properly authorized.  The obligations under this paragraph shall survive
      in perpetuity.</para>
  </section>

  <section id="s1-test" os="test">
    <title>README Feedback Procedure</title>

    <para>(This section will disappear when the final &DISTRO; release is
      created.)</para>

    <para>If you feel that this README could be improved in some way, submit a
      bug report in &RH;'s bug reporting system:</para>

    <para><ulink
    url="https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi">https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi</ulink></para>

    <para>When posting your bug, include the following information in the
      specified fields:</para>

    <itemizedlist>
      <listitem>
        <para><guilabel>Product:</guilabel> &DISTRO;</para>
      </listitem>

      <listitem>
        <para><guilabel>Version:</guilabel> "devel" </para>
      </listitem>

      <listitem>
        <para><guilabel>Component:</guilabel> fedora-release</para>
      </listitem>

      <listitem>
        <para><guilabel>Summary:</guilabel> A short description of what could be
          improved.  If it includes the word "README", so much the
          better.</para>
      </listitem>

      <listitem>
        <para><guilabel>Description:</guilabel> A more in-depth description of
          what could be improved.</para>
      </listitem>

    </itemizedlist>
  </section>

<!--
  <ackno>(
    <emphasis arch="x86">x86</emphasis>
    <emphasis arch="x86_64">x86_64</emphasis>
    )</ackno>
-->
</article>


--- NEW FILE about-fedora.menu ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN"
"http://www.freedesktop.org/standards/menu-spec/menu-1.0.dtd">

<Menu>
  <Name>System</Name>
  <Directory>Desktop.directory</Directory>

  <Include>
    <Category>X-Fedora-About</Category>
  </Include>
</Menu>


--- NEW FILE about-fedora.omf ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE omf PUBLIC "-//OMF//DTD Scrollkeeper OMF Variant V1.0//EN"
"http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-omf.dtd">

<omf>
  <resource>
    <creator>
      fedora-docs-list at redhat.com (Fedora Documentation Project)
    </creator>
    <maintainer>
      fedora-docs-list at redhat.com (Fedora Documentation Project)
    </maintainer>
    <title>
      About Fedora
    </title>
    <date>
      2006-02-14
    </date>
    <version identifier="5.89" date="2006-02-14" description="Fedora Core 5.89"/>
    <subject category="General|Linux|Distributions|Other"/>
    <description>
      Describes Fedora Core, the Fedora Project, and how you can help.
    </description>
    <type>
      About
    </type>
    <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.4//EN"/>
    <identifier url="file:///usr/share/doc/fedora-release-5.89/about/C/about-fedora.xml"/>
    <language code="C"/>
    <relation seriesid="7a5d3ea2-2a1e-11da-86a3-8ea47a4bb227"/>
    <rights type="OPL" license="http://opencontent.org/openpub/" license.version="1.0"/>
  </resource>
</omf>


--- NEW FILE about-fedora.xml ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?> 
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" >

<article>
  <title>About Fedora</title>
  <articleinfo>
    <authorgroup>
      <corpauthor>The Fedora Project community</corpauthor>
      <editor>
	<firstname>Paul</firstname>
	<othername>W.</othername>
	<surname>Frields</surname>
      </editor>
    </authorgroup>
    <copyright>
      <year>2006</year>
      <holder>Fedora Foundation</holder>
    </copyright>
  </articleinfo>
  <para id="pa-about-fedora">
    Fedora is an open, innovative, forward looking operating system and
    platform, based on Linux, that is always free for anyone to use,
    modify and distribute, now and forever. It is developed by a large
    community of people who strive to provide and maintain the very best
    in free, open source software and standards. The Fedora Project is
    managed and directed by the Fedora Foundation and sponsored by Red
    Hat, Inc.
  </para>
  <para>
    Visit the Fedora community Wiki at <ulink
      url="http://fedoraproject.org/wiki/"/>.
  </para>
  <section id="sn-about-extras">
    <title>Fedora Extras</title>
    <para>
      The Fedora Extras project, sponsored by Red Hat and maintained by
      the Fedora community, provides hundreds of high-quality software
      packages to augment the software available in Fedora Core.  Visit
      our Web page at <ulink
	url="http://fedoraproject.org/wiki/Extras"/>.
    </para>
  </section>
  <section id="sn-about-docs">
    <title>Fedora Documentation</title>
    <para>
      The Fedora Documentation Project provides 100% Free/Libre Open
      Source Software (FLOSS) content, services, and tools for
      documentation.  We welcome volunteers and contributors of all
      skill levels.  Visit our Web page at <ulink
	url="http://fedoraproject.org/wiki/DocsProject"/>.
    </para>
  </section>
  <section id="sn-about-translation">
    <title>Fedora Translation</title>
    <para>
      The goal of the Translation Project is to translate the software
      and the documentation associated with the Fedora Project. Visit
      our Web page at <ulink
	url="http://fedora.redhat.com/About/Projects/translations/"/>.
    </para>
  </section>
  <section id="sn-about-legacy">
    <title>Fedora Legacy</title>
    <para>
      The Fedora Legacy Project is a community-supported open source
      project to extend the lifecycle of select 'maintenace mode' Red
      Hat Linux and Fedora Core distributions. Fedora Legacy project is
      a formal Fedora Project supported by the Fedora Foundation and
      sponsored by Red Hat.  Visit our Web page at <ulink
	url="http://fedoraproject.org/wiki/Legacy"/>.
    </para>
  </section>
  <section id="sn-about-triage">
    <title>Fedora Bug Squad</title>
    <para>
      The primary mission of the Fedora Bug Squad is to track down and
      clear bugs in <ulink
	url="https://bugzilla.redhat.com/bugzilla">Bugzilla</ulink> that
      are related to Fedora, and act as a bridge between users and
      developers. Visit our Web page at <ulink
	url="http://fedoraproject.org/wiki/BugZappers"/>.
    </para>
  </section>
  <section id="sn-about-marketing">
    <title>Fedora Marketing</title>
    <para>
      The Fedora Marketing Project is the Fedora Project's public voice.
      Our goal is to promote Fedora and to help promote other Linux and
      open source projects.  Visit our Web page at <ulink
	url="http://fedoraproject.org/wiki/Marketing"/>.
    </para>
  </section>
  <section id="sn-about-ambassadors">
    <title>Fedora Ambassadors</title>
    <para>
      Fedora Ambassadors are people who go to places where other Linux
      users and potential converts gather and tell them about Fedora
      &mdash; the project and the distribution.  Visit our Web page at
      <ulink url="http://fedoraproject.org/wiki/Ambassadors"/>.
    </para>
  </section>
  <section id="sn-about-infrastructure">
    <title>Fedora Infrastructure</title>
    <para>
      The Fedora Infrastructure Project is about helping all Fedora
      contributors get their stuff done with minimum hassle and maximum
      efficiency. Things under this umbrella include the Extras build
      system, the <ulink
	url="http://fedoraproject.org/wiki/Infrastructure/AccountSystem">Fedora 
	Account System</ulink>, the <ulink
	url="http://cvs.fedora.redhat.com/">CVS repositories</ulink>,
      the <ulink url="http://fedoraproject.org/wiki/Communicate">mailing
	lists</ulink>, and the <ulink
	url="http://fedoraproject.org/wiki/Websites">Websites</ulink>
      infrastructure.  Visit our Web site at <ulink
	url="http://fedoraproject.org/wiki/Infrastructure"/>.
    </para>
  </section>
  <section id="sn-about-websites">
    <title>Fedora Websites</title>
    <para>
      The Fedora Websites initiative aims to improve Fedora's image on
      the Internet. The key goals of this effort include:
    </para>
    <itemizedlist>
      <listitem>
	<para>
	  Trying to consolidate all the key Fedora websites onto one
	  uniform scheme
	</para>
      </listitem>
      <listitem>
	<para>
	  Maintaining the content that doesn't fall under any particular
	  sub-project
	</para>
      </listitem>
      <listitem>
	<para>
	  Generally, making the sites as fun and exciting as the project
	  they represent!
	</para>
      </listitem>
    </itemizedlist>
    <para>
      Visit our Web page at <ulink
      url="http://fedoraproject.org/wiki/Websites"/>.
    </para>
  </section>
  <section id="sn-about-artwork">
    <title>Fedora Artwork</title>
    <para>
      Making things look pretty is the name of the game... Icons,
      desktop backgrounds, and themes are all parts of the Fedora
      Artwork Project.  Visit our Web page at <ulink
      url="http://fedoraproject.org/wiki/Artwork"/>.
    </para>
  </section>
  <section id="sn-about-planet">
    <title>Fedora People</title>
    <para>
      You can read weblogs of many Fedora contributors at our official
      aggregator, <ulink url="http://planet.fedoraproject.org/"/>.
    </para>
  </section>
</article>


<!--
Local variables:
mode: xml
fill-column: 72
End:
-->


--- NEW FILE about-gnome.desktop ---
[Desktop Entry]
Encoding=UTF-8
Name=About Fedora
Comment=Learn more about Fedora
Exec=yelp file:///usr/share/doc/fedora-release-5/about/C/about-fedora.xml
Icon=fedora-logo-icon
Terminal=false
Type=Application
Categories=X-Fedora-About;
StartupNotify=true
OnlyShowIn=GNOME;


--- NEW FILE about-kde.desktop ---
[Desktop Entry]
Encoding=UTF-8
GenericName=About Fedora
Name=About Fedora
Comment=Learn more about Fedora
Exec=khelpcenter
Icon=
Path=
Terminal=false
Type=Application
DocPath=khelpcenter/plugins/about.html
Categories=Qt;KDE;Application;Core;
X-KDE-StartupNotify=true
OnlyShowIn=KDE;


--- NEW FILE announcement-release.txt ---
# This file collects notes throughout the release that are
# used for the announcement and/or the splash.xml.

- newer/better/faster/more
- OpenOffice 2.0 pre
- GNOME 2.10
  featuring Clearlooks
- KDE 3.4
- Eclipse & the java stack, in all its huge glory
- Extras by default at release time
- PPC now included
- OO.org 2.0
- Evince first release
- Newer, better GFS fun
- Virtualization available with built-in Xen
- GCC 4.0
- 80 new daemons covered by SELinux (up from a dozen)

Just part of Gnome 2.10, but since it's such a visible change, maybe 
mention the new default theme.



--- NEW FILE eula.py ---
from gtk import *
import string
import gtk
import gobject
import sys
import functions
import rhpl.iconv
import os

##
## I18N
## 
import gettext
gettext.bindtextdomain ("firstboot", "/usr/share/locale")
gettext.textdomain ("firstboot")
_=gettext.gettext

class childWindow:
    #You must specify a runPriority for the order in which you wish your module to run
    runPriority = 15
    moduleName = (_("License Agreement"))

    def launch(self, doDebug = None):
        self.doDebug = doDebug
        if self.doDebug:
            print "initializing eula module"

        self.vbox = gtk.VBox()
        self.vbox.set_size_request(400, 200)

        msg = (_("License Agreement"))

        title_pix = functions.imageFromFile("workstation.png")

        internalVBox = gtk.VBox()
        internalVBox.set_border_width(10)
        internalVBox.set_spacing(5)

        textBuffer = gtk.TextBuffer()
        textView = gtk.TextView()
        textView.set_editable(gtk.FALSE)
        textSW = gtk.ScrolledWindow()
        textSW.set_shadow_type(gtk.SHADOW_IN)
        textSW.set_policy(gtk.POLICY_AUTOMATIC, gtk.POLICY_AUTOMATIC)
        textSW.add(textView)

        lang = os.environ["LANG"]
        if len(string.split(lang, ".")) > 1:
            lang = string.split(lang, ".")[0]

        path = "/usr/share/eula/eula.%s" % lang

        if not os.access(path, os.R_OK):
            #Try to open the translated eula
            lines = open("/usr/share/eula/eula.en_US").readlines()            
        else:
            #If we don't have a translation for this locale, just open the English one
            lines = open(path).readlines()

        iter = textBuffer.get_iter_at_offset(0)

        for line in lines:
            textBuffer.insert(iter, line)
        textView.set_buffer(textBuffer)
            
        self.okButton = gtk.RadioButton(None, (_("_Yes, I agree to the License Agreement")))
        self.noButton = gtk.RadioButton(self.okButton, (_("N_o, I do not agree")))
        self.noButton.set_active(gtk.TRUE)

        internalVBox.pack_start(textSW, gtk.TRUE)
        internalVBox.pack_start(self.okButton, gtk.FALSE)
        internalVBox.pack_start(self.noButton, gtk.FALSE)
        
        self.vbox.pack_start(internalVBox, gtk.TRUE, 5)
        return self.vbox, title_pix, msg

    def apply(self, notebook):
        if self.okButton.get_active() == gtk.TRUE:
            return 0
        else:
            dlg = gtk.MessageDialog(None, 0, gtk.MESSAGE_QUESTION, gtk.BUTTONS_NONE,
                                    (_("Do you want to reread or reconsider the Licence Agreement?  " 
                                       "If not, please shut down the computer and remove this "
                                       "product from your system. ")))

            dlg.set_position(gtk.WIN_POS_CENTER)
            dlg.set_modal(gtk.TRUE)

            continueButton = dlg.add_button(_("_Reread license"), 0)
            shutdownButton = dlg.add_button(_("_Shut down"), 1)
            continueButton.grab_focus()

            rc = dlg.run()
            dlg.destroy()

            if rc == 0:
                return None
            elif rc == 1:
                if self.doDebug:
                    print "shut down system"

                os.system("/sbin/halt")
                return None
                


--- NEW FILE eula.txt ---
			LICENSE AGREEMENT 
			FEDORA(TM) CORE 3 

This agreement governs the download, installation or use of the
Software (as defined below) and any updates to the Software,
regardless of the delivery mechanism. The Software is a collective
work under U.S. Copyright Law.  Subject to the following terms, Fedora
Project grants to the user ("User") a license to this collective work
pursuant to the GNU General Public License.  By downloading,
installing or using the Software, User agrees to the terms of this
agreement.

1.  THE SOFTWARE.  Fedora Core (the "Software") is a modular Linux
    operating system consisting of hundreds of software components.
    The end user license agreement for each component is located in
    the component's source code.  With the exception of certain image
    files containing the Fedora trademark identified in Section 2
    below, the license terms for the components permit User to copy,
    modify, and redistribute the component, in both source code and
    binary code forms.  This agreement does not limit User's rights
    under, or grant User rights that supersede, the license terms of
    any particular component.

2.  INTELLECTUAL PROPERTY RIGHTS.  The Software and each of its
    components, including the source code, documentation, appearance,
    structure and organization are copyrighted by Fedora Project and
    others and are protected under copyright and other laws.  Title to
    the Software and any component, or to any copy, modification, or
    merged portion shall remain with the aforementioned, subject to
    the applicable license.  The "Fedora" trademark is a trademark of
    Red Hat, Inc. ("Red Hat") in the U.S. and other countries and is
    used by permission.  This agreement permits User to distribute
    unmodified copies of Software using the Fedora trademark on the
    condition that User follows Red Hat's trademark guidelines located
    at http://fedora.redhat.com/legal.  User must abide by these
    trademark guidelines when distributing the Software, regardless of
    whether the Software has been modified.  If User modifies the
    Software, then User must replace all images containing the
    "Fedora" trademark.  Those images are found in the anaconda-images
    and the fedora-logos packages.  Merely deleting these files may
    corrupt the Software.

3.  LIMITED WARRANTY.  Except as specifically stated in this agreement
    or a license for a particular component, TO THE MAXIMUM EXTENT
    PERMITTED UNDER APPLICABLE LAW, THE SOFTWARE AND THE COMPONENTS
    ARE PROVIDED AND LICENSED "AS IS" WITHOUT WARRANTY OF ANY KIND,
    EXPRESSED OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF
    MERCHANTABILITY, NON-INFRINGEMENT OR FITNESS FOR A PARTICULAR
    PURPOSE.  Neither the Fedora Project nor Red Hat warrants that the
    functions contained in the Software will meet User's requirements
    or that the operation of the Software will be entirely error free
    or appear precisely as described in the accompanying
    documentation.  USE OF THE SOFTWARE IS AT USER'S OWN RISK.

4.  LIMITATION OF REMEDIES AND LIABILITY. TO THE MAXIMUM EXTENT
    PERMITTED BY APPLICABLE LAW, FEDORA PROJECT AND RED HAT WILL NOT
    BE LIABLE TO USER FOR ANY DAMAGES, INCLUDING INCIDENTAL OR
    CONSEQUENTIAL DAMAGES, LOST PROFITS OR LOST SAVINGS ARISING OUT OF
    THE USE OR INABILITY TO USE THE SOFTWARE, EVEN IF FEDORA PROJECT
    OR RED HAT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

5.  EXPORT CONTROL.  As required by U.S. law, User represents and
    warrants that it: (a) understands that the Software is subject to
    export controls under the U.S. Commerce Department's Export
    Administration Regulations ("EAR"); (b) is not located in a
    prohibited destination country under the EAR or U.S. sanctions
    regulations (currently Cuba, Iran, Iraq, Libya, North Korea, Sudan
    and Syria); (c) will not export, re-export, or transfer the
    Software to any prohibited destination, entity, or individual
    without the necessary export license(s) or authorizations(s) from
    the U.S. Government; (d) will not use or transfer the Software for
    use in any sensitive nuclear, chemical or biological weapons, or
    missile technology end-uses unless authorized by the
    U.S. Government by regulation or specific license; (e) understands
    and agrees that if it is in the United States and exports or
    transfers the Software to eligible end users, it will, as required
    by EAR Section 741.17(e), submit semi-annual reports to the
    Commerce Department's Bureau of Industry & Security (BIS), which
    include the name and address (including country) of each
    transferee; and (f) understands that countries other than the
    United States may restrict the import, use, or export of
    encryption products and that it shall be solely responsible for
    compliance with any such import, use, or export restrictions.

6.  GENERAL.  If any provision of this agreement is held to be
    unenforceable, that shall not affect the enforceability of the
    remaining provisions.  This agreement shall be governed by the
    laws of the State of North Carolina and of the United States,
    without regard to any conflict of laws provisions, except that the
    United Nations Convention on the International Sale of Goods shall
    not apply.

Copyright (C) 2003, 2004 Fedora Project.  All rights reserved.  "Red Hat"
and "Fedora" are trademarks of Red Hat, Inc.  "Linux" is a registered
trademark of Linus Torvalds.  All other trademarks are the property of
their respective owners.


--- NEW FILE fedora-devel.repo ---
[development]
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
enabled=0


--- NEW FILE fedora-release-notes.spec ---
Name:           fedora-release-notes
Version:        
Release:        1%{?dist}
Summary:        

Group:          
License:        
URL:            
Source0:        
BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

BuildRequires:  
Requires:       

%description


%prep
%setup -q


%build
%configure
make %{?_smp_mflags}


%install
rm -rf $RPM_BUILD_ROOT
make install DESTDIR=$RPM_BUILD_ROOT


%clean
rm -rf $RPM_BUILD_ROOT


%files
%defattr(-,root,root,-)
%doc



%changelog


--- NEW FILE fedora-release.spec ---
%define builtin_release_version @VERSION@
%define builtin_release_name @RELNAME@
%define real_release_version %{?release_version}%{!?release_version:%{builtin_release_version}}
%define real_release_name %{?release_name}%{!?release_name:%{builtin_release_name}}
Summary: Fedora Core release file
Name: fedora-release
Version: %{real_release_version}
Release: 9
Copyright: GFDL
Group: System Environment/Base
Source: fedora-release-%{builtin_release_version}- at RELARCH@.tar.gz
Obsoletes: rawhide-release
Obsoletes: redhat-release
Obsoletes: indexhtml
Provides: redhat-release
Provides: indexhtml
BuildRoot: %{_tmppath}/fedora-release-root
ExclusiveArch: @RELARCH@

%description
Fedora Core release file

%prep
%setup -q -n fedora-release- at VERSION@- at RELARCH@

%build
python -c "import py_compile; py_compile.compile('eula.py')"

%install
rm -rf $RPM_BUILD_ROOT
mkdir -p $RPM_BUILD_ROOT/etc
echo "Fedora Core release %{real_release_version} (%{real_release_name})" > $RPM_BUILD_ROOT/etc/fedora-release
cp $RPM_BUILD_ROOT/etc/fedora-release $RPM_BUILD_ROOT/etc/issue
echo "Kernel \r on an \m" >> $RPM_BUILD_ROOT/etc/issue
cp $RPM_BUILD_ROOT/etc/issue $RPM_BUILD_ROOT/etc/issue.net
echo >> $RPM_BUILD_ROOT/etc/issue
ln -s fedora-release $RPM_BUILD_ROOT/etc/redhat-release
mkdir -p $RPM_BUILD_ROOT/usr/share/eula $RPM_BUILD_ROOT/usr/share/firstboot/modules
cp -f eula.txt $RPM_BUILD_ROOT/usr/share/eula/eula.en_US
cp -f eula.py $RPM_BUILD_ROOT/usr/share/firstboot/modules/eula.py

mkdir -p -m 755 $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML
cp -ap img css \
  $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML
for file in indexhtml-*.html ; do
  newname=`echo $file | sed 's|indexhtml-\(.*\)-\(.*\).html|index-\2.html|g'`
  install -m 644 $file $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML/$newname || :
done
mv -f $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML/index-en.html \
  $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML/index.html || :

mkdir -p -m 755 $RPM_BUILD_ROOT/etc/sysconfig/rhn
mkdir -p -m 755 $RPM_BUILD_ROOT/etc/yum.repos.d
install -m 644 sources $RPM_BUILD_ROOT/etc/sysconfig/rhn/sources
for file in fedora*repo ; do
  install -m 644 $file $RPM_BUILD_ROOT/etc/yum.repos.d
done

%clean
rm -rf $RPM_BUILD_ROOT

# If this is the first time a package containing /etc/issue
# is installed, we want the new files there. Otherwise, we
# want %config(noreplace) to take precedence.
%triggerpostun  -- redhat-release < 7.1.93-1
for I in issue issue.net; do
	if [ -f /etc/$I.rpmnew ] ; then
	   mv -f /etc/$I /etc/$I.rpmsave
	   mv -f /etc/$I.rpmnew /etc/$I
	fi
done

%files
%defattr(-,root,root)
%attr(0644,root,root) /etc/fedora-release
/etc/redhat-release
%dir /etc/sysconfig/rhn
%dir /etc/yum.repos.d
%config(noreplace) /etc/sysconfig/rhn/sources
%config(noreplace) /etc/yum.repos.d/*
%doc R*
%doc eula.txt GPL autorun-template
%config %attr(0644,root,root) /etc/issue
%config %attr(0644,root,root) /etc/issue.net
/usr/share/firstboot/modules/eula.py
/usr/share/eula/eula.en_US
%{_defaultdocdir}/HTML


--- NEW FILE fedora-updates-testing.repo ---
[updates-testing]
name=Fedora Core $releasever - $basearch - Test Updates
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/$releasever/$basearch/
mirrorlist=http://fedora.redhat.com/download/mirrors/updates-testing-fc$releasever
enabled=0
gpgcheck=1


--- NEW FILE fedora-updates.repo ---
[updates-released]
name=Fedora Core $releasever - $basearch - Released Updates
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/$basearch/
mirrorlist=http://fedora.redhat.com/download/mirrors/updates-released-fc$releasever
enabled=1
gpgcheck=1


--- NEW FILE fedora.repo ---
[base]
name=Fedora Core $releasever - $basearch - Base
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-$releasever
enabled=1
gpgcheck=1


--- NEW FILE files-map.txt ---
# map of how XML files in the release-notes module interact

RELEASE-NOTES-*.xml
    fdp-info-*.xml
        ../../docs-common/common/legalnotice-relnotes-*.xml
    Welcome-*.xml
    OverView-*.xml
    ../../docs-common/common/legalnotice-*.xml
    Feedback-*.xml
    Introduction-*.xml
    Installer-*.xml
    ArchSpecific-*.xml
        ArchSpecificPPC-*.xml
        ArchSpecificx86-*.xml
        ArchSpecificx86_64-*.xml
    Networking-*.xml
    PackageNotes-*.xml
        ServerTools-*.xml
        PackageNotesJava-*.xml
        Kernel-*.xml
        Security-*.xml
            SecuritySELinux-*.xml
        DevelopmentTools-*.xml
            DevelopmentToolsJava-*.xml
            DevelopmentToolsGCC-*.xml
        I18n-*.xml
        Printing-*.xml
        DatabaseServers-*.xml
        Multimedia-*.xml
        WebServers-*.xml
        Samba-*.xml
        Xorg-*.xml
        Entertainment-*.xml
    Legacy-*.xml
    PackageChanges-*.xml
    ProjectOverview-*.xml
    Colophon-*.xml

# Unused, but maybe we should use/

BackwardsCompatibility-*.xml
Desktop-*.xml
FileSystems-*.xml
FileServers-*.xml
SystemDaemons-*.xml






--- NEW FILE main.xsl ---
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:exsl="http://exslt.org/common"
		version="1.0"
                exclude-result-prefixes="exsl">

<xsl:import href="readmes.xsl"/>
<xsl:import href="/usr/share/sgml/docbook/xsl-stylesheets/html/chunk-common.xsl"/>
<xsl:include href="/usr/share/sgml/docbook/xsl-stylesheets/html/manifest.xsl"/>

<!-- Why is chunk-code now xsl:included?

Suppose you want to customize *both* the chunking algorithm used *and* the
presentation of some elements that may be chunks. In order to do that, you
must get the order of imports "just right". The answer is to make your own
copy of this file, where you replace the initial import of "docbook.xsl"
with an import of your own base.xsl (that does its own import of docbook.xsl).

Put the templates for changing the presentation of elements in your base.xsl.

Put the templates that control chunking after the include of chunk-code.xsl.

Voila! (Man I hope we can do this better in XSLT 2.0)

-->

<!-- don't show TOC for article because html viewer in anaconda doesn't support the dt and dl tags -->
<xsl:param name="generate.toc">
article nop
</xsl:param>

<xsl:include href="/usr/share/sgml/docbook/xsl-stylesheets/html/profile-docbook.xsl"/>

<xsl:param name="onechunk" select="1"/>

<xsl:output method="html" encoding="utf-8" indent="no"/>

</xsl:stylesheet>


--- NEW FILE readmes.xsl ---
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:fo="http://www.w3.org/1999/XSL/Format"
                version='1.0'>

<xsl:output method="html" encoding="UTF-8" indent="no"/>

<!-- This sets the extension for HTML files to ".html".     -->
<!-- (The stylesheet's default for XHTML files is ".xhtm".) -->
<xsl:param name="html.ext" select="'.html'"/>

<!-- This sets the filename based on the ID.                -->
<xsl:param name="use.id.as.filename" select="'0'"/>
<xsl:param name="suppress.navigation" select="'1'"/>
<xsl:param name="generate.toc">
article nop
</xsl:param>
<xsl:param name="chapter.autolabel" select="'0'"/>

<xsl:template match="command">
  <xsl:call-template name="inline.monoseq"/>
</xsl:template>

<xsl:template match="application">
  <xsl:call-template name="inline.boldseq"/>
</xsl:template>

<xsl:template match="guibutton">
  <xsl:call-template name="inline.boldseq"/>
</xsl:template>

<xsl:template match="guiicon">
  <xsl:call-template name="inline.boldseq"/>
</xsl:template>

<xsl:template match="guilabel">
  <xsl:call-template name="inline.boldseq"/>
</xsl:template>

<xsl:template match="guimenu">
  <xsl:call-template name="inline.boldseq"/>
</xsl:template>

<xsl:template match="guimenuitem">
  <xsl:call-template name="inline.boldseq"/>
</xsl:template>

<xsl:template match="guisubmenu">
  <xsl:call-template name="inline.boldseq"/>
</xsl:template>

<xsl:template match="filename">
  <xsl:call-template name="inline.monoseq"/>
</xsl:template>

</xsl:stylesheet>


--- NEW FILE refactoring-notes.txt ---
## $Id:

Questions?  Email to fedora-docs-list at redhat.com.


0. Make a back-up of the *-en.xml files, if you need them for
   reference.  The content is all present in the new files, but it may
   be easier for you to have the old files for reference.

1. Be sure to have newest files in the release-notes and docs-common
   module.  'cvs up -d' can help to make sure you get new files.

2. All languages except en have been removed from the Makefile target:

   LANGUAGES      	= en #it ja_JP ru zh_CN
                        # uncomment languages when you have all the same
                        # fies localized as are listed in XMLEXTRAFILES

   As the comments say, when you are ready to test the build for your
   language, move the language code to the left of the #comment mark
   and run 'make html'.

3. Old files are left in place for you to use.  You can take the
   existing translation and move it to the new location.  When you are
   done, or let us know on fedora-docs-list at redhat.com and the old
   files will get cleaned up.

4. Some of the old language specific files have been renamed.  In the
   cases where content has been split into multiple files or the file
   is new, a blank file has been created.  You need to move content
   from the old file into the new file, as per the table below.

5. This table shows the name of the old file and the name of the new
   file.  This conversion has been done for -en only.  Three old files
   on the left have been split into two or more files on the right.
   They are development-tools*xml, security*xml, and splash*xml.

Old filename				New filename
=============================================================
[New File]				ArchSpecific-en.xml
[New File]				ArchSpecificPPC-en.xml
[New File]				ArchSpecificx86-en.xml
[New File]				ArchSpecificx86_64-en.xml
[New File]				BackwardsCompatibility-en.xml
colophon-relnotes-en.xml		Colophon-en.xml
daemons-en.xml				SystemDaemons-en.xml
database-servers-en.xml			DatabaseServers-en.xml
desktop-en.xml				Desktop-en.xml
development-tools-en.xml		DevelopmentTools-en.xml
					DevelopmentToolsGCC-en.xml
					DevelopmentToolsJava-en.xml
entertainment-en.xml			Entertainment-en.xml
file-servers-en.xml			FileServers-en.xml
file-systems-en.xml			FileSystems-en.xml
hardware-reqs-en.xml			[Deleted] [Content is in ArchSpecific*]
i18n-en.xml				I18n-en.xml
install-notes-en.xml			Installer-en.xml
intro-en.xml				Introduction-en.xml
java-package-en.xml			PackageNotesJava-en.xml
kernel-en.xm				Kernel-en.xml
legacy-en.xml				Legacy-en.xml
misc-server-en.xml			[Deleted]
multimedia-en.xml			Multimedia-en.xml
networking-en.xml			Networking-en.xml
overview-en.xml				OverView-en.xml
package-movement-en.xml			PackageChanges-en.xml
package-notes-en.xml			PackageNotes-en.xml
printing-en.xml				Printing-en.xml
project-overview-en.xml			ProjectOverview-en.xml
README-en.xml				[Ignore]
RELEASE-NOTES-en.xml			[Same]
RELEASE-NOTES-master-en.xml		[Deleted]
samba-en.xml				Samba-en.xml
security-en.xml				Security-en.xml
					SecuritySELinux-en.xml
server-tools-en.xml			ServerTools-en.xml
splash-en.xml				Welcome-en.xml
  (content split into:)			OverView-en.xml
web-servers-en.xml			WebServers-en.xml
xorg-en.xml				Xorg-en.xml




--- NEW FILE rpm-info.xml ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<!DOCTYPE rpm-info SYSTEM "../../docs-common/packaging/rpm-info.dtd">

<rpm-info>
  <colophon>
    <worker id="fdp" wholename="Fedora Documentation Project"
      email="fedora-docs-list at redhat.com" surname="Project" firstname="Fedora
      Documentation" initials="fdp"/>
    <worker id="quaid" wholename="Karsten Wade" email="kwade at redhat.com"
      surname="Wade" firstname="Karsten" initials="quaid"/>
    <worker email="Tommy.Reynolds at MegaCoder.com" firstname="Tommy"
      id="megacoder" initials="JTR" surname="Reynolds" wholename="Tommy
      Reynolds"/>
    <worker id="PaulWFrields" wholename="Paul W. Frields"
      email="stickster at gmail.com" surname="Frields" firstname="Paul"
      othername="W." initials="PWF"/>
  </colophon>
  <author worker="fdp"/>
  <license>
    <rights>OPL</rights>
    <version>1.0</version>
  </license>
  <copyright>
    <year>2006</year>
    <holder>Red Hat, Inc. and others</holder>
  </copyright>
  <titles>
    <translation lang="en">
      <title>Fedora Core 5 Release Notes</title>
      <desc>Important information about this release of Fedora Core</desc>
    </translation>
<!--PLEASE ADD A TRANSLATION FOR EACH ADDITIONAL LANGUAGE.-->
    <translation lang="zh_CN">
      <title>Fedora Core 5 发行注记</title>
      <desc></desc>
    </translation>
    <translation lang="it">
      <title>Note di rilascio per Fedora Core 5</title>
      <desc></desc>
    </translation>
    <translation lang="ru">
      <title>Fedora Core 5 Замечания к выпуску</title>
      <desc></desc>
    </translation>
    <translation lang="ja_JP">
      <title>Fedora Core 5 リリースノート</title>
      <desc></desc>
    </translation>
  </titles>
  <changelog order="newest-first">
    <revision date="2006-05-28" number="0.5.0.2" role="doc">
      <author worker="PaulWFrields"/>
      <details lang="en_US">Refer to IG and fix repodata instructions
	(#186904)</details>
    </revision>
    <revision date="2006-04-14" number="0.5.0.1" role="doc">
      <author worker="quaid"/>
      <details lang="en_US">Errata release notes for FC5 release.</details>
    </revision>
    <revision date="2006-02-28" number="0.5.0.0" role="doc">
      <author worker="quaid"/>
      <details lang="en_US">Finished port of wiki for FC5 release.</details>
    </revision>
  </changelog>
</rpm-info>


--- NEW FILE sources ---
### This describes the various package repositories (repos) that up2date will
### query for packages. It currently supports apt-rpm, yum, and "dir" repos.

### Format is one repository (repo) entry per line, # starts comments, the
### first word on each line is the type of repo.

### The default RHN (using "default" as the url means use the one in the 
### up2date config file).
#up2date default

### Note: when a channel label is required for the non up2date repos,
### the label is solely used as an internal identifier and is not
### based on the url or any other info from the repos.

### An apt style repo (the example is arjan's 2.6 kernel repo).
### The format is:
### type  channel-label      service:server	    path        repo name
#apt arjan-2.6-kernel-i386 http://people.redhat.com ~arjanv/2.5/ kernel

### Note: for apt repos, there can be multiple repo names specified (space
### seperated).

### A yum style repo. The format is:
### type  channel-label     url 

yum fedora-core-3 http://download.fedora.redhat.com/pub/fedora/linux/core/3/$ARCH/os/ 
yum updates-released-fc3 http://download.fedora.redhat.com/pub/fedora/linux/core/updates/3/$ARCH/

yum-mirror fedora-core-3 http://fedora.redhat.com/download/up2date-mirrors/fedora-core-3
yum-mirror updates-released-fc3 http://fedora.redhat.com/download/up2date-mirrors/updates-released-fc3

#yum updates-testing http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/3/$ARCH/
#yum-mirror updates-testing http://fedora.redhat.com/download/up2date-mirrors/updates-testing-fc3

#yum development http://download.fedora.redhat.com/pub/fedora/linux/core/development/$ARCH/
#yum-mirror development http://fedora.redhat.com/download/up2date-mirrors/fedora-core-rawhide

### A local directory full of packages (a "dir" repo). For example:
#dir my-favorite-rpms /var/spool/RPMS/

# Multiple versions of all repos except "up2date" can be used. Dependencies
# can be resolved "cross-repo" if need be.





More information about the docs-commits mailing list