Browsing Louisiana French translation

11.

The format described here is used since Debian 0.93; details of the old format are described in B<deb-old>(5).

12.

FORMAT

13.

The file is an B<ar> archive with a magic value of B<!E<lt>archE<gt>>. The file names might contain a trailing slash.

14.

The B<tar> archives currently allowed are, the old-style (v7) format, the pre-POSIX ustar format, a subset of the GNU format (only the new style long pathnames and long linknames, supported since dpkg 1.4.1.17), and the POSIX ustar format (long names supported since dpkg 1.15.0). Unrecognized tar typeflags are considered an error.

15.

The first member is named B<debian-binary> and contains a series of lines, separated by newlines. Currently only one line is present, the format version number, B<2.0> at the time this manual page was written. Programs which read new-format archives should be prepared for the minor number to be increased and new lines to be present, and should ignore these if this is the case.

16.

If the major number has changed, an incompatible change has been made and the program should stop. If it has not, then the program should be able to safely continue, unless it encounters an unexpected member in the archive (except at the end), as described below.

17.

The second required member is named B<control.tar.gz>. It is a gzipped tar archive containing the package control information, as a series of plain files, of which the file B<control> is mandatory and contains the core control information. The control tarball may optionally contain an entry for `B<.>', the current directory.

18.

The third, last required member is named B<data.tar>. It contains the filesystem as a tar archive, either not compressed (supported since dpkg 1.10.24), or compressed with gzip (with B<.gz> extension), xz (with B<.xz> extension, supported since dpkg 1.15.6), bzip2 (with B<.bz2> extension, supported since dpkg 1.10.24) or lzma (with B<.lzma> extension, supported since dpkg 1.13.25).

19.

These members must occur in this exact order. Current implementations should ignore any additional members after B<data.tar>. Further members may be defined in the future, and (if possible) will be placed after these three. Any additional members that may need to be inserted before B<data.tar> and which should be safely ignored by older programs, will have names starting with an underscore, `B<_>'.

20.

Those new members which won't be able to be safely ignored will be inserted before B<data.tar> with names starting with something other than underscores, or will (more likely) cause the major version number to be increased.