<affiliate group="MSYS Developer Toolkit" />
<description lang="en" title="bzip2: a high-quality data compressor">
<paragraph>bzip2 is a freely available, patent free (see below),
-high-quality data compressor. It typically compresses files to within
-10% to 15% of the best available techniques (the PPM family of statistical
-compressors), whilst being around twice as fast at compression and six
-times faster at decompression. This package provides the utility programs
-and scripts.</paragraph>
+ high-quality data compressor. It typically compresses files
+ to within 10% to 15% of the best available techniques (the
+ PPM family of statistical compressors), whilst being around
+ twice as fast at compression and six times faster at
+ decompression. This package provides the utility programs and
+ scripts.
+ </paragraph>
</description>
<component class="bin">
<!-- Note that the bzip2 utilities are linked against the static
- version of libbz2.a, so there is no -dll dependency here. -->
+ version of libbz2.a, so there is no -dll dependency here. -->
<release tarname="bzip2-1.0.5-1-msys-1.0.11-bin.tar.gz" />
<release tarname="bzip2-1.0.5-2-msys-1.0.13-bin.tar.lzma" />
- <requires eq="msys-msysCORE-*-msys-*-bin.tar" />
+ <requires eq="msys-core-*-msys-*-bin.tar" />
</component>
<component class="doc">
<release tarname="bzip2-1.0.5-1-msys-1.0.11-doc.tar.gz" />
<affiliate group="MSYS Developer Toolkit" />
<description lang="en" title="libbz2: runtime library for bzip2">
<paragraph>bzip2 is a freely available, patent free (see below),
-high-quality data compressor. It typically compresses files to within
-10% to 15% of the best available techniques (the PPM family of statistical
-compressors), whilst being around twice as fast at compression and six
-times faster at decompression. This package provides the runtime library
-and development files.</paragraph>
+ high-quality data compressor. It typically compresses files
+ to within 10% to 15% of the best available techniques (the
+ PPM family of statistical compressors), whilst being around
+ twice as fast at compression and six times faster at
+ decompression. This package provides the runtime library and
+ development files.
+ </paragraph>
</description>
<component class="dll">
<release tarname="libbz2-1.0.5-1-msys-1.0.11-dll-1.tar.gz" />
<release tarname="libbz2-1.0.5-2-msys-1.0.13-dll-1.tar.lzma" />
- <requires eq="msys-msysCORE-*-msys-*-bin.tar" />
+ <requires eq="msys-core-*-msys-*-bin.tar" />
</component>
<component class="dev">
<release tarname="libbz2-1.0.5-1-msys-1.0.11-dev.tar.gz" />
<affiliate group="MSYS Developer Toolkit" />
<description lang="en" title="crypt: tools for DES encryption">
<paragraph>crypt provides a library implementing the standard
-encryption functions crypt(), encrypt(), and setkey(). Many programs,
-such as perl, rely on the presence of these functions; as the functions
-are not provided by the MSYS runtime, this additional library fulfils
-those needs.</paragraph>
+ encryption functions crypt(), encrypt(), and setkey(). Many
+ programs, such as perl, rely on the presence of these functions;
+ as the functions are not provided by the MSYS runtime, this
+ additional library fulfils those needs.
+ </paragraph>
<paragraph>crypt also provides a command-line tool for exercising
-those functions. `crypt cleartext' generates an encrypted version of the
-cleartext using a random salt. `crypt salt cleartext' encrypts cleartext
-using the specified salt. Salt is a two-character string which also appears as the first two
-characters of the encrypted cleartext.</paragraph>
- <paragraph>The msys-crypt package provides the command-line
-utility crypt and related documentation. The associated msys-libcrypt
-package provides the runtime library and related development files.</paragraph>
+ those functions. `crypt cleartext' generates an encrypted version
+ of the cleartext using a random salt. `crypt salt cleartext'
+ encrypts cleartext using the specified salt. Salt is a two-character
+ string which also appears as the first two characters of the
+ encrypted cleartext.
+ </paragraph>
+ <paragraph>The msys-crypt package provides the command-line utility
+ crypt and related documentation. The associated msys-libcrypt
+ package provides the runtime library and related development files.
+ </paragraph>
</description>
<component class="bin">
<!-- Note that the crypt utility is linked against the static
version of libcrypt.a, so there is no -dll dependency here. -->
<release tarname="crypt-1.1_1-2-msys-1.0.11-bin.tar.lzma" />
<release tarname="crypt-1.1_1-3-msys-1.0.13-bin.tar.lzma" />
- <requires eq="msys-msysCORE-*-msys-*-bin.tar" />
+ <requires eq="msys-core-*-msys-*-bin.tar" />
</component>
<component class="doc">
<release tarname="crypt-1.1_1-2-msys-1.0.11-doc.tar.lzma" />
<affiliate group="MSYS Developer Toolkit" />
<description lang="en" title="libcrypt: runtime library for crypt">
<paragraph>crypt provides a library implementing the standard
-encryption functions crypt(), encrypt(), and setkey(). Many programs,
-such as perl, rely on the presence of these functions; as the functions
-are not provided by the MSYS runtime, this additional library fulfils
-those needs.</paragraph>
+ encryption functions crypt(), encrypt(), and setkey(). Many
+ programs, such as perl, rely on the presence of these functions;
+ as the functions are not provided by the MSYS runtime, this
+ additional library fulfils those needs.
+ </paragraph>
<paragraph>crypt also provides a command-line tool for exercising
-those functions. `crypt cleartext' generates an encrypted version of the
-cleartext using a random salt. `crypt salt cleartext' encrypts cleartext
-using the specified salt. Salt is a two-character string which also appears as the first two
-characters of the encrypted cleartext.</paragraph>
+ those functions. `crypt cleartext' generates an encrypted version
+ of the cleartext using a random salt. `crypt salt cleartext'
+ encrypts cleartext using the specified salt. Salt is a two-character
+ string which also appears as the first two characters of the
+ encrypted cleartext.
+ </paragraph>
<paragraph>The msys-libcrypt package provides the libcrypt runtime
-library and related development files. The associated msys-crypt package
-provides the command-line utility crypt and related documentation.</paragraph>
+ library and related development files. The associated msys-crypt
+ package provides the command-line utility crypt and related
+ documentation.
+ </paragraph>
</description>
<component class="dll">
<release tarname="libcrypt-1.1_1-2-msys-1.0.11-dll-0.tar.lzma" />
<release tarname="libcrypt-1.1_1-3-msys-1.0.13-dll-0.tar.lzma" />
- <requires eq="msys-msysCORE-*-msys-*-bin.tar" />
+ <requires eq="msys-core-*-msys-*-bin.tar" />
</component>
<component class="dev">
<release tarname="libcrypt-1.1_1-2-msys-1.0.11-dev.tar.lzma" />
<affiliate group="MSYS Developer Toolkit" />
<description lang="en" title="lndir: Xorg recursive directory symlink tool">
<paragraph>The lndir program makes a shadow copy of a directory
-tree, except that the shadow is not populated with real files but instead
-with symbolic links (*) pointing at the real files in the original
-directory tree. This is usually useful building applications outside their
-source directory, when the build machinery does not directly support that
-behavior. You can build in the shadow tree, and the object files will be
-in the shadow directory, while the source files in the shadow directory
-are just symlinks (*) to the real files.</paragraph>
- <paragraph>(*) On MSYS, instead of symbolic links the shadow
-tree is populated with hardlinks to the original files whenever possible,
-and with copies if not (e.g. the original and destination directories are
-on different devices, or the file system is not NTFS).</paragraph>
+ tree, except that the shadow is not populated with real files but
+ instead with symbolic links (*) pointing at the real files in the
+ original directory tree. This is usually useful building
+ applications outside their source directory, when the build
+ machinery does not directly support that behavior. You can build
+ in the shadow tree, and the object files will be in the shadow
+ directory, while the source files in the shadow directory are just
+ symlinks (*) to the real files.
+ </paragraph>
+ <paragraph>(*) On MSYS, instead of symbolic links the shadow tree is
+ populated with hardlinks to the original files whenever possible,
+ and with copies if not (e.g. the original and destination directories
+ are on different devices, or the file system is not NTFS).
+ </paragraph>
</description>
<component class="bin">
<release tarname="lndir-1.0.1-1-msys-1.0.11-bin.tar.gz" />
<release tarname="lndir-1.0.1-2-msys-1.0.13-bin.tar.lzma" />
- <requires eq="msys-msysCORE-*-msys-*-bin.tar" />
+ <requires eq="msys-core-*-msys-*-bin.tar" />
</component>
<component class="doc">
<release tarname="lndir-1.0.1-1-msys-1.0.11-doc.tar.gz" />
<package name="msys-zlib">
<affiliate group="MSYS Developer Toolkit" />
<description lang="en" title="ZLib: A Massively Spiffy Yet Delicately Unobtrusive Compression Library">
- <paragraph>The zlib compression library provides in-memory compression and decompression functions, including integrity checks of the uncompressed data.</paragraph>
+ <paragraph>The zlib compression library provides in-memory
+ compression and decompression functions, including integrity checks
+ of the uncompressed data.
+ </paragraph>
</description>
- <!-- note: for historical reasons, the zlib dll component does not specify a soname -->
+ <!-- note: for historical reasons, the zlib dll component does not
+ specify a soname -->
<component class="dll">
<release tarname="zlib-1.2.3-1-msys-1.0.11-dll.tar.gz" />
<release tarname="zlib-1.2.3-2-msys-1.0.13-dll.tar.lzma" />
- <requires eq="msys-msysCORE-*-msys-*-bin.tar" />
+ <requires eq="msys-core-*-msys-*-bin.tar" />
</component>
<component class="dev">
<release tarname="zlib-1.2.3-1-msys-1.0.11-dev.tar.gz" />
OSDN Git Service
