release-notes legacy-en.xml, 1.1, 1.2 package-notes-en.xml, 1.4, 1.5 security-en.xml, 1.2, 1.3 splash-en.xml, 1.3, 1.4 web-servers-en.xml, 1.2, 1.3 xorg-en.xml, 1.2, 1.3
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Wed Nov 23 06:56:04 UTC 2005
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10120
Modified Files:
legacy-en.xml package-notes-en.xml security-en.xml
splash-en.xml web-servers-en.xml xorg-en.xml
Log Message:
Last of the transfer of content from the Wiki, time to tag, build, and post.
Index: legacy-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/legacy-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legacy-en.xml 25 Oct 2005 08:34:00 -0000 1.1
+++ legacy-en.xml 23 Nov 2005 06:55:57 -0000 1.2
@@ -1,3 +1,50 @@
+<section id="sn-legacy">
+ <title>Legacy Information</title>
+
+ <note>
+ <title><command>Slocate</command> has been replaced with
+ <command>mlocate</command> in this release.</title>
+ <para>
+ The <command>/usr/bin/{locate,updatedb}</command>
+ implementation <command>slocate</command> was replaced by mlocate.
+ </para>
+ </note>
+ <itemizedlist>
+ <listitem>
+ <para>The <command>locate</command> command should be completely
+ compatible.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <listitem>
+ <para><filename>/etc/updatedb.conf</filename> is compatible for correct
+ configuration files
+ </para>
+ </listitem>.
+ <listitem>
+ <para>Syntax errors that <command>slocate</command> would not
+ detect are now reported.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The <envar>DAILY_UPDATE</envar> variable is not
+ supported.
+ </para>
+ </listitem>
+ <listitem>
+ <para>The <command>updatedb</command> command is not compatible, custom
+ scripts using <command>updatedb</command> might have to be
+ changed.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ The LinuxThreads library, which has been deprecated in &FC; 4, is no
+ longer available in this release. NPTL has been the default
+ threading library since Red Hat Linux 9.
+ </para>
+</section>
<!--
Local variables:
mode: xml
Index: package-notes-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/package-notes-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- package-notes-en.xml 25 Oct 2005 19:40:56 -0000 1.4
+++ package-notes-en.xml 23 Nov 2005 06:55:57 -0000 1.5
@@ -114,6 +114,7 @@
<command>auditctl -e 1</command>
</screen>
</section>
+<!--
<section id="sn-nptl">
<title>LinuxThreads versus NPTL</title>
<para>
@@ -178,6 +179,7 @@
In general, conversion to using NPTL has not been an issue.
</para>
</section>
+ -->
<section>
<title>Enabling the <filename>slocate</filename> Database</title>
<para>
@@ -233,18 +235,7 @@
<option>~/.ssh/config</option> file.
</para>
</section>
- <section id="sn-perl">
- <title>Perl Binary Compat Symlinks</title>
- <para>
- Binary compat symlinks for <filename>perl-5.8.0</filename>,
- <filename>perl-5.8.1</filename>, and
- <filename>perl-5.8.2</filename> have been removed. If you have
- perl modules built with those older versions of perl, you need
- to rebuild using the <filename>perl-5.8.6</filename> contained
- in &FC; &LOCALVER;.
- </para>
- </section>
- &SERVER-TOOLS;
+<!-- &SERVER-TOOLS; -->
&JAVA-PACKAGE;
</section>
<section id="sn-packages-core">
@@ -253,16 +244,6 @@
This section contains the most elemental components of &DISTRO;,
including the kernel.
</para>
- <section>
- <title>yum</title>
- <para>
- The sqllite database is now used by yum, and makes performance
- noticeably faster.
- </para>
- <para>
- The Fedora Extras repository is now enabled by default.
- </para>
- </section>
&KERNEL;
&SECURITY;
</section>
Index: security-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/security-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- security-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ security-en.xml 23 Nov 2005 06:55:57 -0000 1.3
@@ -4,15 +4,44 @@
This section highlights various security items from &FC;.
</para>
<para>
- <computeroutput>Pam_stack</computeroutput> is deprecated. More
- details available from fedora-test-list (<ulink
- url="http://www.redhat.com/mailman/listinfo/fedora-test-list">http://www.redhat.com/mailman/listinfo/fedora-test-list</ulink>
+ <computeroutput>Pam_stack</computeroutput> is deprecated. Linux-PAM
+ 0.78 and later contain the include directive that obsoletes the
+ <computeroutput>pam_stack</computeroutput> module.
+ <computeroutput>pam_stack</computeroutput> module usage is logged
+ with a deprecation warning. It might be removed in a future
+ release.
</para>
<section id="sn-security-highlights">
<title>Security Highlights</title>
<para>
This section highlights various security items from &FC;.
</para>
+ <variablelist>
+ <varlistentry>
+ <term>Buffer Overflow detection and variable reordering</term>
+ <listitem>
+ <para>For this release, all of the software in the &FC; and
+ &FEX; software repositories is compiled using a security
+ feature called <firstterm>fstack-protecter</firstterm>.
+ fstack-protector puts a canary value on the stack of
+ <computeroutput>key</computeroutput> functions. Just before
+ the return address and just before returning from that
+ value, that canary value is verified. If there was a buffer
+ overflow, the canary no longer matches and the program
+ aborts. The canary value is random for each time the
+ application is started and makes it impossible to guess
+ remotely. This is a security feature that has been
+ backported from GCC 4.1 to the version of the GCC compiler
+ used in &FC; &FCVER;.
+ </para>
+ <para>
+ This is in addition to using <envar>FORTIFY_SOURCE</envar>
+ from &FC; 4 onwards.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <section>
<para>
Digital certificates are now centralised in directories
under <filename>/etc/pki/</filename>. Users performing an upgrade must
Index: splash-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/splash-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- splash-en.xml 25 Oct 2005 09:07:12 -0000 1.3
+++ splash-en.xml 23 Nov 2005 06:55:57 -0000 1.4
@@ -1,18 +1,33 @@
<section id="sn-splash">
<title>Welcome to &FC; &LOCALVER;</title>
- <caution>
- <title>Information Out-of-Date</title>
- <para>
- The content in this section needs to be updated for &DISTRO;
- &DISTROVER;
- </para>
- </caution>
<para>
&FC; is a completely free, user friendly, and secure general purpose
- platform based on Linux. The &FP; is an open source project that
- pioneers leading edge technology and concepts sponsored by &RH; and
+ platform based on Linux that is always free for anyone to use,
+ modify, and distribute, now and forever. The &FP; is an open source project that
+ pioneers leading edge technology and concepts, which is sponsored by &RH; and
supported by the &FED; community.
</para>
+ <caution>
+ <title>This is a test release, not intended for end-users</title>
+ <para>
+ This is a test release and is provided for developers and testers
+ to participate and provide feedback. It is not meant for end
+ users.
+ </para>
+ <para>
+ Subscribe to the fedora-test and fedora-devel mailings lists to
+ keep track of important changes in the current development
+ versions and provide feedback to the developers. &FP; requests you
+ to file bug reports and enhancements to provide a improved final
+ release to end users. For more information on this, refer to the
+ following document:
+ </para>
+ <para>
+ <ulink
+ url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink>.
+
+ </para>
+ </caution>
<tip>
<title>Latest Release Notes on the Web</title>
<para>
@@ -39,13 +54,11 @@
Refer to these webpages to find out more information about &FED;:
</para>
<itemizedlist>
-<!-- FIXME Return when the section is updated
<listitem>
<para>
<xref linkend="sn-new-in-fc"/>
</para>
</listitem>
--->
<listitem>
<para>
<xref linkend="sn-intro"/> — Technical release notes
@@ -70,6 +83,67 @@
</para>
</listitem>
</itemizedlist>
+ <section id="sn-new-in-fc">
+ <title>What's New In &FC; &FCVER;</title>
+ <itemizedlist>
+ <listitem>
+ <para>Xen Virtualisation software and yum package manager are
+ now well integrated within the &FED; installer. The installer
+ interface is more streamlined. Remote logging and improved
+ support for tracebacks is included.
+ </para>
+ </listitem>
+ <listitem>
+ <para><application>Pup</application>, a graphical updater using
+ yum, has replaced <application>rhn-applet</application>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>GNOME 2.12 and KDE 3.4 desktop environments are
+ available.
+ </para>
+ </listitem>
+ <listitem>
+ <para>GNOME Power Manager and GNOME Screensaver are available as
+ a technology preview within this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ OpenOffice.org 2.0 final release is included. OpenOffice.org
+ now uses system versions for many of the libraries leading to
+ increased performance and efficiency.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Xorg X11R7 release candidate 2 has been included in this
+ release. This is the first modular version, which helps in
+ providing additional features and bug fixes at a faster pace.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Kernel 2.6.14 is included. Software suspend is enabled in this
+ release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>SCIM has replaced IIMF in &FC; in this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>There are changes in the animated mouse cursor theme.
+ </para>
+ </listitem>
+ <listitem>
+ <para>&FP; now has a new logo.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>The proposed plans for Fedora in this version are available
+ from <ulink
+ url='http://fedoraproject.org/wiki/RoadMap'>http://fedoraproject.org/wiki/RoadMap</ulink>.
+ </para>
+ </section>
<!-- commented out until the content can be updated
<section id="sn-new-in-fc">
<title>New in &FC; &LOCALVER;</title>
Index: web-servers-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/web-servers-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- web-servers-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ web-servers-en.xml 23 Nov 2005 06:55:57 -0000 1.3
@@ -6,7 +6,7 @@
<section>
<title><command>httpd</command></title>
<para>
- The following changes have been made to the default <command></command>httpd
+ The following changes have been made to the default <command>httpd</command>
configuration:
</para>
<itemizedlist>
@@ -18,7 +18,7 @@
</listitem>
<listitem>
<para>The <computeroutput>mod_ext_filter</computeroutput> module
- is now loaded by default
+ is now loaded by default.
</para>
</listitem>
</itemizedlist>
Index: xorg-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/xorg-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- xorg-en.xml 25 Oct 2005 08:34:00 -0000 1.2
+++ xorg-en.xml 23 Nov 2005 06:55:57 -0000 1.3
@@ -1,211 +1,162 @@
<section id="sn-xwindows">
<title>X Window System (Graphics)</title>
- <caution>
- <title>Information Out-of-Date</title>
- <para>
- The content in this section needs to be updated for &DISTRO;
- &DISTROVER;
- </para>
- </caution>
- <para>
- This section contains information related to the X Window System
- implementation provided with &DISTRO;.
- </para>
- <section id="sn-xwindows-xorg">
- <title><filename>xorg-x11</filename></title>
- <para>
- Users new to the X.org X11 implementation should take note of a
- few differences between it and the XFree86.org X11 implementation
- which shipped in previous &RH; and &FED; operating systems. In
- particular, the names of some files have changed:
- </para>
- <para>
- X Server Binary:
- </para>
- <itemizedlist>
- <listitem>
- <para>XFree86 X11: <filename>XFree86</filename></para>
- </listitem>
- <listitem>
- <para>X.org X11: <filename>Xorg</filename></para>
- </listitem>
- </itemizedlist>
- <para>
- X Server Configuration File:
- </para>
- <itemizedlist>
- <listitem>
- <para>XFree86 X11:
- <filename>/etc/X11/XF86Config</filename></para>
- </listitem>
- <listitem>
- <para>X.org X11: <filename>/etc/X11/xorg.conf</filename></para>
- </listitem>
- </itemizedlist>
- <para>
- X Server Log File:
- </para>
- <itemizedlist>
- <listitem>
- <para>XFree86 X11:
- <filename>/var/log/XFree86.<replaceable>$DISPLAY</replaceable>.log</filename></para>
- </listitem>
- <listitem>
- <para>X.org X11:
- <filename>/var/log/Xorg.<replaceable>$DISPLAY</replaceable>.log</filename></para>
- </listitem>
- </itemizedlist>
- <para>
- When configuring or troubleshooting your X server
- configuration, be sure that you are using the correct
- files.
- </para>
- <para>
- There has been some confusion regarding font-related issues
- under the X Window System in recent versions of &DISTRO; (and
- versions of &RHL; before it.) At the present time, there are two
- font subsystems, each with different characteristics:
- </para>
- <itemizedlist>
- <listitem>
- <para>The original (15+ year old) subsystem is referred to as
- the <firstterm>core X font subsystem</firstterm>. Fonts
- rendered by this subsystem are not anti-aliased, are handled
- by the X server, and have names such as:
- <computeroutput>-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1</computeroutput>
- </para>
- </listitem>
- <listitem>
- <para>
- The newer font subsystem is known as
- <firstterm>fontconfig</firstterm>, and allows applications
- direct access to the font files. Fontconfig is often used
- along with the <filename>Xft</filename> library, which allows
- applications to render fontconfig fonts to the screen with
- antialiasing. Fontconfig uses more human-friendly names such
- as: <computeroutput>Luxi Sans-10</computeroutput>
- </para>
- </listitem>
- </itemizedlist>
- <para>
- Over time, fontconfig and <filename>Xft</filename> will replace
- the core X font subsystem. At the present time, applications
- using the Qt 3 or GTK 2 toolkits (which would include KDE and
- GNOME applications) use the fontconfig and Xft font subsystem;
- almost everything else uses the core X fonts.
- </para>
- <para>
- In the future, &FC; may support only fontconfig/Xft in
- place of the XFS font server as the default local font access
- method.
- </para>
- <note>
- <title>Note</title>
+ <section>
+ <title>Docs/Beats/Xorg</title>
+ <para/>
+ </section>
+ <section>
+ <title>X Window System (Graphics)</title>
+ <para>This section contains information related to the X Window
+ System implementation provided with &FED;.
+ </para>
+ <section id="sn-xorg-x11">
+ <title>xorg-x11</title>
+ <para>X.org X11 is an open source implementation of the X Window
+ System. It provides the basic low level functionality that full
+ fledged graphical user interfaces (GUIs) such as GNOME and KDE
+ are designed upon. </para>
+ <para>For more information about Xorg refer to <ulink
+ url='http://xorg.freedesktop.org/wiki/'>http://xorg.freedesktop.org/wiki/</ulink>
+ </para>
+ <para>You can use
+ <guimenu>Applications</guimenu><guimenuitem>System
+ Settings</guimenuitem><guimenuitem>Display</guimenuitem> or
+ run <command>system-config-display</command> to configure the
+ settings. The configuration file for Xorg is located in
+ <filename>/etc/X11/xorg.conf</filename>.
+ </para>
<para>
- An exception to the font subsystem usage outlined above is
- OpenOffice.org, which uses its own font rendering technology.
+ Modular X.Org X11R7 RC2 was released into &FED; development
+ (<firstterm>rawhide</firstterm>) on November 16, 2005. This is
+ the first modular release of Xorg. Among several benefits,
+ modular Xorg enables users to receive updates at a faster pace,
+ while helping developers to develop and release specific
+ components in a rapid fashion.
</para>
- </note>
- <para>
- The steps to add new fonts to &DISTRO; &DISTROVER; depend on the
- fonts subsystem this is going to use the new fonts. For the core X
- font subsystem:
- </para>
-
- <procedure>
- <step>
- <para>
- Create the <filename>/usr/share/fonts/local/</filename>
- directory (if it doesn't already exist):
- </para>
-<screen>
-<command>mkdir /usr/share/fonts/local/</command>
-</screen>
- </step>
- <step>
- <para>
- Copy the new font file into
- <filename>/usr/share/fonts/local/</filename>
- </para>
- </step>
- <step>
- <para>
- Update the font information by issuing the following commands
- (note that, due to formatting restrictions, the following
- commands may appear on more than one line; in use, each
- command should be entered on a single line):
- </para>
-<screen>
-<command>ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</command>
-<command>mkfontdir /usr/share/fonts/local/</command>
-</screen>
- </step>
- <step>
- <para>
- If you had to create
- <filename>/usr/share/fonts/local/</filename>, you must then
- add it to the X font server (<command>xfs</command>) path:
- </para>
-<screen>
-<command>chkfontpath --add /usr/share/fonts/local/</command>
-</screen>
- </step>
- </procedure>
- <para>
- Adding new fonts to the fontconfig font subsystem is more
- straightforward; the new font file only needs to be copied into
- the <filename>/usr/share/fonts/</filename> directory (individual
- users can modify their personal font configuration by copying the
- font file into the <filename>~/.fonts/</filename> directory).
- </para>
- <para>
- After the new font has been copied, use
- <command>fc-cache</command> to update the font information cache:
- </para>
-<screen>
-<command>fc-cache <replaceable><directory></replaceable></command>
-</screen>
- <para>
- (Where
- <command><replaceable><directory></replaceable></command>
- would be either the <filename>/usr/share/fonts/</filename> or
- <filename>~/.fonts/</filename> directories.)
- </para>
- <para>
- Individual users may also install fonts graphically, by browsing
- <command>fonts:///</command> in
- <application>Nautilus</application>, and dragging the new font
- files there.
- </para>
- <note>
- <title>Note</title>
<para>
- If the font filename ends with "<filename>.gz</filename>", it
- has been compressed with <command>gzip</command>, and must be
- decompressed (with the <command>gunzip</command> command) before
- the fontconfig font subsystem can use the font.
+ More information on the current status of the Xorg
+ modularization effort in &FED; is available from <ulink
+ url='/Xorg/Modularization'>http://fedoraproject.org/wiki/Xorg/Modularization</ulink>
</para>
- </note>
- <para>
- Due to the transition to the new font system based on
- fontconfig/Xft, GTK+ 1.2 applications are not affected by any
- changes made via the <guilabel>Font Preferences</guilabel> dialog.
- For these applications, a font can be configured by adding the
- following lines to the file <filename>~/.gtkrc.mine</filename>:
- </para>
-<screen>
-<computeroutput>style "user-font" {
-fontset = "<replaceable><font-specification></replaceable>"
-}
-widget_class "*" style "user-font"</computeroutput>
-</screen>
- <para>
- (Where
- <command><replaceable><font-specification></replaceable></command>
- represents a font specification in the style used by traditional X
- applications, such as
- "<computeroutput>-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</computeroutput>".)
- </para>
+ </section>
+ <section id="sn-xorg-x11r7-dev">
+ <title>Xorg X11R7 Developer Notes</title>
+ <para>X11R7 RC2 is included in this release and there are a number
+ of things that software developers, and packagers in &FED;
+ repositories, need to be aware of in order to ensure that their
+ software or software packages properly compile and work with
+ X11R7. Some are simple changes, while others may be more
+ involved. Here is a summary of issues that may arise and where
+ possible, suggestions on how to fix them.
+ </para>
+ <section>
+ <title>The <filename>/usr/X11R6</filename> directory hierarchy</title>
+ <para>
+ X11R7 installs into <filename>/usr</filename> directly now,
+ and no longer uses the <filename>/usr/X11R6</filename>
+ hierarchy. Applications that rely on files being present at
+ fixed paths under <filename>/usr/X11R6</filename> at compile
+ time or at run time, must be updated to use the system
+ <envar>PATH</envar>, or some other mechanism, to dynamically
+ determine where the files reside, or alternatively to hard
+ code the new locations, possibly with fallbacks.
+ </para>
+ </section>
+ <section>
+ <title><command>Imake</command></title>
+ <para><command>Imake</command> is no longer used to build the X
+ Window System, and as such is now officially deprecated.
+ <command>Imake</command>, <command>xmkmf</command> and other
+ utilities previously supplied by the X Window System, are
+ still supplied in X11R7, however X.Org highly recommends that
+ people migrate from Imake to using GNU autotools and
+ <filename>pkg-config</filename>. Support for
+ <command>imake</command> may vanish in a future X Window
+ System release, so developers are strongly encouraged to
+ transition away from it, and not to use it for any new
+ software projects.
+ </para>
+ </section>
+ <section>
+ <title>The systemwide app-defaults directory</title>
+ <para>The system app-defaults directory for X resources, is now
+ <filename>%{_datadir}/X11/app-defaults</filename>, which
+ expands to <filename>/usr/share/X11/app-defaults</filename> on
+ &FC; &FCVER; and for future &RHEL; systems. </para>
+ </section>
+ <section id="sn-xorg-xft-config">
+ <title><filename>xft-config</filename> can't be found</title>
+ <para>Modular X now uses GNU autotools, and
+ <command>pkg-config</command> for its buildsystem
+ configuration, etc. <command>xft-config</command> has been
+ deprecated for two to three years, and
+ <command>pkgconfig</command> <filename>*.pc</filename> files
+ have been provided for most of this time. Applications that
+ previously used <command>xft-config</command> to obtain the
+ <option>Cflags</option> or libs options for building with,
+ must now be updated to use <command>pkg-config</command>.
+ </para>
+ </section>
+ </section>
+ <section id="sn-xorg-devel-overview">
+ <title>Xorg X11R7 Developer Overview</title>
+ <para>Here is a short list of some of the more developer/package
+ visible changes that are present in X11R7: </para>
+ <itemizedlist>
+ <listitem>
+ <para>The entire buildsystem has changed from
+ <command>Imake</command> to the GNU autotools collection.
+ </para>
+ </listitem>
+ <listitem>
+ <para>All of the libraries now install
+ <command>pkgconfig</command> <filename>*.pc</filename>
+ files, which should now always be used by software that
+ depends on these libraries, instead of hard coding paths to
+ them in <filename>/usr/X11R6/lib</filename> or elsewhere.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Everything is now installed directly into
+ <filename>/usr</filename> instead of
+ <filename>/usr/X11R6</filename>. All software that hard
+ codes paths to anything in <filename>/usr/X11R6</filename>,
+ must now be changed preferably to dynamically detect the
+ proper location of the object, or to hard code the new paths
+ that X11R7 uses by default. It is strongly advised to use
+ autodetection methods rather than to hard code paths.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Every library has its own, private source package now,
+ which creates a runtime binary subpackage, and a -devel
+ subpackage.
+ </para>
+ <para>
+ Any software package that previously picked up the
+ development headers, etc. for X libraries by using
+ <computeroutput>BuildRequires:
+ (XFree86-devel|xorg-x11-devel)</computeroutput>, must now
+ individually list each library dependency individually. When
+ doing this, it is greatly preferred and strongly recommended
+ to use <firstterm>virtual</firstterm> build dependencies instead of hard coding
+ the library package names of the Xorg implementation.
+ </para>
+ <para>
+ This means you should use: <computeroutput>BuildRequires:
+ libXft-devel</computeroutput> instead of using:
+ <filename>BuildRequires: xorg-x11-Xft-devel</filename>. If
+ your software truly does depend on the X.Org X11
+ implementation of a specific library, and there is no other
+ clean/safe way to state the dependency, then use the
+ <filename>xorg-x11--devel</filename> form. By sticking to
+ the virtual provides/requires mechanism, this makes it
+ painless if and when the libraries move to another location
+ in the future.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
</section>
</section>
More information about the docs-commits
mailing list