Added X as an optional dependency for libungif-4.1.0b1

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@2423 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
Randy McMurchy 2004-07-06 05:11:12 +00:00
parent e5785364ab
commit a249d64e6f

View File

@ -19,22 +19,23 @@
<sect2>
<title>Introduction to <application>libungif</application></title>
<para>The libungif package contains libraries for reading all
<acronym>GIF</acronym>s and writing non-compressed ones as well as programs for
converting and working with <acronym>GIF</acronym> files. The libraries are
useful for any graphics program wishing to deal with <acronym>GIF</acronym>
files while the programs are useful for conversion purposes as well as cleaning
up images.</para>
<para>The <application>libungif</application> package contains libraries for
reading all <acronym>GIF</acronym>s and writing non-compressed ones as well as
programs for converting and working with <acronym>GIF</acronym> files. The
libraries are useful for any graphics program wishing to deal with
<acronym>GIF</acronym> files while the programs are useful for conversion
purposes as well as cleaning up images.</para>
<para>The reason libungif only writes non-compressed <acronym>GIF</acronym>s
is due to a legal issue with <acronym>LZW</acronym> compression (which Unisys
claims a patent on). Reading <acronym>GIF</acronym>s is not a problem as the
decompression routines do not seem to be limited in this way. Note that this
has in the past been disputed. The best way to avoid this whole mess is to
simply use libungif for looking at <acronym>GIF</acronym> images on the web,
while in any pages which you design, use the open source <acronym>PNG</acronym>
format instead (which uses, not surprisingly, the libpng library) which has no
patent issues at all.</para>
<para>The reason <application>libungif</application> only writes non-compressed
<acronym>GIF</acronym>s is due to a legal issue with <acronym>LZW</acronym>
compression (which Unisys claims a patent on). Reading <acronym>GIF</acronym>s
is not a problem as the decompression routines do not seem to be limited in
this way. Note that this has in the past been disputed. The best way to avoid
this whole mess is to simply use <application>libungif</application> for
looking at <acronym>GIF</acronym> images on the web, while in any pages which
you design, use the open source <acronym>PNG</acronym> format instead (which
uses, not surprisingly, the <application>libpng</application> library) which
has no patent issues at all.</para>
<sect3><title>Package information</title>
<itemizedlist spacing='compact'>
@ -52,6 +53,11 @@ url="&patch-root;/libungif-&libungif-version;-va_start-1.patch"/></para></listit
</itemizedlist>
</sect3>
<sect3><title><application>libungif</application> dependencies</title>
<sect4><title>Optional</title>
<para>X (<xref linkend="xfree86"/> or <xref linkend="xorg"/>)</para></sect4>
</sect3>
</sect2>
<sect2>
@ -107,8 +113,8 @@ printers.</para></sect3>
</para></sect3>
<sect3><title>gif2rgb</title>
<para>Convert images saved as <acronym>GIF</acronym> to 24-bit <acronym>RGB
</acronym> image(s).</para></sect3>
<para>Convert images saved as <acronym>GIF</acronym> to 24-bit
<acronym>RGB</acronym> image(s).</para></sect3>
<sect3><title>gifasm</title>
<para>Assemble multiple <acronym>GIF</acronym>s into one, or burst a
@ -168,7 +174,8 @@ pipelines.</para></sect3>
<acronym>GIF</acronym>.</para></sect3>
<sect3><title>gifpos</title>
<para>Change a GIF's screen size or recondition it.</para></sect3>
<para>Change a <acronym>GIF</acronym>'s screen size or recondition
it.</para></sect3>
<sect3><title>gifrotat</title>
<para>Rotate a <acronym>GIF</acronym> through any desired angle.</para></sect3>