| 1 |
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> |
| 2 |
<software-distribution project="MinGW" home="http://mingw.org" issue="2012073100"> |
| 3 |
|
| 4 |
<!-- File: msys-libarchive.xml --> |
| 5 |
|
| 6 |
<package-collection subsystem="msys"> |
| 7 |
<download-host uri="http://prdownloads.sourceforge.net/mingw/%F?download" /> |
| 8 |
|
| 9 |
<package name="msys-libarchive"> |
| 10 |
<description lang="en" title="library for handling various archive formats" > |
| 11 |
<paragraph>libarchive is a programming library that can create and |
| 12 |
read several different streaming archive formats, including most |
| 13 |
popular tar variants and several cpio formats, mtree, and ar |
| 14 |
archives. It can also read shar, zip, jar, and xar archives, as |
| 15 |
well as ISO9660 CDROM images. It automatically handles gzip, |
| 16 |
bzip2, compress, xz, and lzma compression and decompression, as |
| 17 |
well as uudecode decompression. The bsdtar program is an |
| 18 |
implementation of tar(1) that is built on top of libarchive. |
| 19 |
</paragraph> |
| 20 |
<paragraph>This MSYS port of libarchive differs from the MinGW |
| 21 |
version also provided by the MinGW/MSYS project. In addition |
| 22 |
to requiring the MSYS runtime library, this implementation |
| 23 |
supports mtree data and understands MSYS's "unix" style pathnames. |
| 24 |
It also supports archives that contain symbolic links by |
| 25 |
converting them to equivalent hardlink (or recursive copy) |
| 26 |
representations (see msys-bsdtar for more information). The MinGW |
| 27 |
implementation does not support archives with symbolic links, nor |
| 28 |
mtree data. It does, however, operate properly on systems where |
| 29 |
MSYS is not installed. Both msys-libarchive and mingw32-libarchive |
| 30 |
(and their associated bsdtar and bsdcpio subpackages) depend on |
| 31 |
additional DLLs such as msys-liblzma (mingw32-liblzma), etc. |
| 32 |
There is, in addition, a MinGW package that provides a standalone |
| 33 |
version of bsdtar which has no external dependencies and only |
| 34 |
limited functionality: mingw32-basic-bsdtar (see its documentation |
| 35 |
for more information). |
| 36 |
</paragraph> |
| 37 |
<paragraph>The msys-libarchive package provides the runtime |
| 38 |
library, development files, and documentation for libarchive. |
| 39 |
The associated msys-bsdtar package provides an implementation |
| 40 |
of tar(1) based on libarchive, while the associated msys-bsdcpio |
| 41 |
package provides a similar implementation of cpio(1). |
| 42 |
</paragraph> |
| 43 |
</description> |
| 44 |
|
| 45 |
<licence tarname="libarchive-%-msys-%-lic.tar.%" /> |
| 46 |
<source tarname="libarchive-%-msys-%-src.tar.%" /> |
| 47 |
|
| 48 |
<component class="doc"> |
| 49 |
<release tarname="libarchive-2.8.3-1-msys-1.0.13-doc.tar.lzma" /> |
| 50 |
</component> |
| 51 |
|
| 52 |
<component class="lic"> |
| 53 |
<release tarname="libarchive-2.8.3-1-msys-1.0.13-lic.tar.lzma" /> |
| 54 |
</component> |
| 55 |
|
| 56 |
<component class="dev"> |
| 57 |
<requires eq="msys-libbz2-*-msys-*-dev.tar" /> |
| 58 |
<requires eq="msys-liblzma-*-msys-*-dev.tar" /> |
| 59 |
<requires eq="msys-libopenssl-*-msys-*-dev.tar" /> |
| 60 |
<requires eq="msys-libxml2-*-msys-*-dev.tar" /> |
| 61 |
<requires eq="msys-zlib-*-msys-*-dev.tar" /> |
| 62 |
<release tarname="libarchive-2.8.3-1-msys-1.0.13-dev.tar.lzma" > |
| 63 |
<requires eq="msys-libarchive-%-msys-%-dll-2.tar" /> |
| 64 |
</release> |
| 65 |
</component> |
| 66 |
|
| 67 |
<component class="dll"> |
| 68 |
<release tarname="libarchive-2.8.3-1-msys-1.0.13-dll-2.tar.lzma" > |
| 69 |
<requires eq="msys-libbz2-*-msys-*-dll-1.tar" /> |
| 70 |
<requires eq="msys-liblzma-*-msys-*-dll-1.tar" /> |
| 71 |
<requires eq="msys-libopenssl-*-msys-*-dll-100.tar" /> |
| 72 |
<requires eq="msys-libxml2-*-msys-*-dll-2.tar" /> |
| 73 |
<requires eq="msys-zlib-*-msys-*-dll.tar" /> |
| 74 |
</release> |
| 75 |
|
| 76 |
<!-- Every MSYS DLL package requires msys-core-bin --> |
| 77 |
<requires eq="msys-core-*-msys-*-bin.tar" /> |
| 78 |
</component> |
| 79 |
</package> |
| 80 |
|
| 81 |
<package name="msys-bsdtar"> |
| 82 |
<affiliate group="MinGW Developer Toolkit" /> |
| 83 |
<description lang="en" title="BSD version of the tar utility" > |
| 84 |
<paragraph>The msys-bsdtar package provides an implementation |
| 85 |
of tar(1) based on libarchive, which manipulates streaming archive |
| 86 |
files -- including the eponymous tar format. However, bsdtar |
| 87 |
can also extract from tar, pax, cpio, zip, jar, ar, xar, mtree, |
| 88 |
and ISO 9660 cdrom images, as well as create tar, pax, cpio, ar, |
| 89 |
mtree, and shar archives. It supports automatic detection and |
| 90 |
handling of .gz, .bz2, .lzma, .xz, and .Z decompression (and |
| 91 |
compression). It supports ustar, pax, and GNU tar formats. |
| 92 |
</paragraph> |
| 93 |
<paragraph>This MSYS port of bsdtar differs from the MinGW version |
| 94 |
also provided by the MinGW/MSYS project. In addition to requiring |
| 95 |
the MSYS runtime library, this implementation supports mtree data |
| 96 |
and understands MSYS's "unix" style pathnames. It also supports |
| 97 |
archives that contain symbolic links by converting them to |
| 98 |
equivalent hardlink (or recursive copy) representations (see |
| 99 |
below). The MinGW implementation does not support archives with |
| 100 |
symbolic links, nor mtree data. It does, however, operate properly |
| 101 |
on systems where MSYS is not installed. Both msys-bsdtar and |
| 102 |
mingw32-bsdtar depend on additional DLLs such as msys-libarchive |
| 103 |
(mingw32-liblzma), etc. There is, in addition, a MinGW package |
| 104 |
that provides a standalone version of bsdtar which has no external |
| 105 |
dependencies and only limited functionality: mingw32-basic-bsdtar |
| 106 |
(see its documentation for more information). |
| 107 |
</paragraph> |
| 108 |
<paragraph>This msys implementation has some unique behaviors with |
| 109 |
regards to symbolic and hard links. When creating archives on an |
| 110 |
MSYS platform, there are no symbolic links; hardlinks are archived |
| 111 |
as on unix, without requiring duplicate storage (unless the |
| 112 |
--hard-dereference option is used). When extracing archives on |
| 113 |
an MSYS platform, if the archive contains hardlinks then they are |
| 114 |
reproduced on the local file system provided the Win32 filesystem |
| 115 |
supports hardlinks (e.g. NTFS; on FAT, a duplicate copy of the |
| 116 |
file is created). If the archive contains symbolic links where |
| 117 |
the target is a file contained within the archive itself, then |
| 118 |
those links are reproduced as if they were hardlinks, as described |
| 119 |
above. "Dangling" symbolic links are not supported. Symbolic |
| 120 |
links to directories within the archive are "supported", by |
| 121 |
creating a recursive copy of the target directory, where the |
| 122 |
contents of the directory are treated as hardlinks as described |
| 123 |
above. |
| 124 |
</paragraph> |
| 125 |
<paragraph>This msys implementation ignores ownership data and |
| 126 |
permission bits; all extracted files are created as if owned |
| 127 |
by the current user, regardless of the current user's root |
| 128 |
(Administrator) status. All archived files are added to the |
| 129 |
archive with "default" permission and as if owned by the current |
| 130 |
user. |
| 131 |
</paragraph> |
| 132 |
<paragraph>libarchive is a programming library that can create and |
| 133 |
read several different streaming archive formats, including most |
| 134 |
popular tar variants and several cpio formats, mtree, and ar |
| 135 |
archives. It can also read shar, zip, jar, and xar archives, as |
| 136 |
well as ISO9660 CDROM images. It automatically handles gzip, |
| 137 |
bzip2, compress, xz, and lzma compression and decompression, as |
| 138 |
well as uudecode decompression. The bsdtar program is an |
| 139 |
implementation of tar(1) that is built on top of libarchive. |
| 140 |
</paragraph> |
| 141 |
<paragraph>The msys-bsdtar package provides an implementation |
| 142 |
of tar(1) based on libarchive, while the associated msys-bsdcpio |
| 143 |
package provides a similar implementation of cpio(1). The |
| 144 |
associated msys-libarchive package provides the runtime |
| 145 |
library, development files, and documentation. |
| 146 |
</paragraph> |
| 147 |
</description> |
| 148 |
|
| 149 |
<licence tarname="libarchive-%-msys-%-lic.tar.%" /> |
| 150 |
<source tarname="libarchive-%-msys-%-src.tar.%" /> |
| 151 |
|
| 152 |
<component class="bin"> |
| 153 |
<!-- Every MSYS package requires msys-core-bin. This dependency |
| 154 |
is not explicitly stated here; rather, it is implicitly satisfied |
| 155 |
as a prerequisite of the matching DLL for this package itself, |
| 156 |
which is specified for each of the following releases. |
| 157 |
--> |
| 158 |
<release tarname="bsdtar-2.8.3-1-msys-1.0.13-bin.tar.lzma" > |
| 159 |
<requires eq="msys-libarchive-%-msys-%-dll-2.tar" /> |
| 160 |
</release> |
| 161 |
</component> |
| 162 |
</package> |
| 163 |
|
| 164 |
<package name="msys-bsdcpio"> |
| 165 |
<affiliate group="MinGW Developer Toolkit" /> |
| 166 |
<description lang="en" title="BSD version of the cpio utility" > |
| 167 |
<paragraph>The msys-bsdcpio package provides an implementation |
| 168 |
of cpio(1) based on libarchive, which copies files between |
| 169 |
archives and directories. This implementation can extract from |
| 170 |
tar, pax, cpio, zip, jar, ar, mtree, xar, and ISO 9660 cdrom |
| 171 |
images, as well as create tar, pax, cpio, ar, and shar archives. |
| 172 |
It supports automatic detection and handling of .gz, .bz2, .lzma, |
| 173 |
.xz, and .Z decompression (and compression). It supports the old |
| 174 |
POSIX.1 portable cpio format (odc), the new SVR4 portable cpio |
| 175 |
format (newc), as well as the POSIX.1 pax and ustar formats. |
| 176 |
</paragraph> |
| 177 |
<paragraph>This MSYS port of bsdcpio differs from the MinGW version |
| 178 |
also provided by the MinGW/MSYS project. In addition to requiring |
| 179 |
the MSYS runtime library, this implementation supports mtree data |
| 180 |
and understands MSYS's "unix" style pathnames. It also supports |
| 181 |
archives that contain symbolic links by converting them to |
| 182 |
equivalent hardlink (or recursive copy) representations (see |
| 183 |
below). The MinGW implementation does not support archives with |
| 184 |
symbolic links. It does, however, operate properly on systems |
| 185 |
where MSYS is not installed. Both msys-bsdcpio and mingw32-bsdcpio |
| 186 |
depend on additional DLLs such as msys-libarchive (mingw32-liblzma), |
| 187 |
etc. |
| 188 |
</paragraph> |
| 189 |
<paragraph>This msys implementation has some unique behaviors with |
| 190 |
regards to symbolic and hard links. When creating archives on an |
| 191 |
MSYS platform, there are no symbolic links; hardlinks are archived |
| 192 |
as on unix, without requiring duplicate storage (unless the |
| 193 |
--hard-dereference option is used). When extracing archives on |
| 194 |
an MSYS platform, if the archive contains hardlinks then they are |
| 195 |
reproduced on the local file system provided the Win32 filesystem |
| 196 |
supports hardlinks (e.g. NTFS. On FAT, a duplicate copy of the |
| 197 |
file is created). If the archive contains symbolic links where |
| 198 |
the target is a file contained within the archive itself, then |
| 199 |
those links are reproduced as if they were hardlinks, as described |
| 200 |
above. "Dangling" symbolic links are not supported. Symbolic |
| 201 |
links to directories within the archive are "supported", by |
| 202 |
creating a recursive copy of the target directory, where the |
| 203 |
contents of the directory are treated as hardlinks as described |
| 204 |
above. |
| 205 |
</paragraph> |
| 206 |
<paragraph>This msys implementation ignores ownership data and |
| 207 |
permission bits; all extracted files are created as if owned |
| 208 |
by the current user, regardless of the current user's root |
| 209 |
(Administrator) status. All archived files are added to the |
| 210 |
archive with "default" permission and as if owned by the current |
| 211 |
user. |
| 212 |
</paragraph> |
| 213 |
<paragraph>libarchive is a programming library that can create and |
| 214 |
read several different streaming archive formats, including most |
| 215 |
popular tar variants and several cpio formats, mtree, and ar |
| 216 |
archives. It can also read shar, zip, jar, and xar archives, as |
| 217 |
well as ISO9660 CDROM images. It automatically handles gzip, |
| 218 |
bzip2, compress, xz, and lzma compression and decompression, as |
| 219 |
well as uudecode decompression. The bsdcpio program is an |
| 220 |
implementation of cpio(1) that is built on top of libarchive. |
| 221 |
</paragraph> |
| 222 |
<paragraph>The msys-bsdcpio package provides an implementation |
| 223 |
of cpio(1) based on libarchive, while the associated msys-bsdtar |
| 224 |
package provides a similar implementation of tar(1). The |
| 225 |
associated msys-libarchive package provides the runtime |
| 226 |
library, development files, and documentation. |
| 227 |
</paragraph> |
| 228 |
</description> |
| 229 |
|
| 230 |
<licence tarname="libarchive-%-msys-%-lic.tar.%" /> |
| 231 |
<source tarname="libarchive-%-msys-%-src.tar.%" /> |
| 232 |
|
| 233 |
<component class="bin"> |
| 234 |
<!-- Every MSYS package requires msys-core-bin. This dependency |
| 235 |
is not explicitly stated here; rather, it is implicitly satisfied |
| 236 |
as a prerequisite of the matching DLL for this package itself, |
| 237 |
which is specified for each of the following releases. |
| 238 |
--> |
| 239 |
<release tarname="bsdcpio-2.8.3-1-msys-1.0.13-bin.tar.lzma" > |
| 240 |
<requires eq="msys-libarchive-%-msys-%-dll-2.tar" /> |
| 241 |
</release> |
| 242 |
</component> |
| 243 |
</package> |
| 244 |
|
| 245 |
</package-collection> |
| 246 |
</software-distribution> |
| 247 |
<!-- vim: set nocompatible expandtab fileformat=unix textwidth=80 tabstop=2 shiftwidth=2: --> |
