Linux Commands Examples

A great documentation place for Linux commands

dpkg-scanpackages

create Packages index files


see also : dpkg - dpkg-scansources

Synopsis

dpkg-scanpackages [option...] binary-dir [override-file [path-prefix]] > Packages


add an example, a script, a trick and tips

: email address (won't be displayed)
: name

Step 2

Thanks for this example ! - It will be moderated and published shortly.

Feel free to post other examples
Oops ! There is a tiny cockup. A damn 404 cockup. Please contact the loosy team who maintains and develops this wonderful site by clicking in the mighty feedback button on the side of the page. Say what happened. Thanks!

examples

0
source
            
dpkg-scanpackages -m debs >Packages
bzip2 -zkf Packages

description

dpkg-scanpackages sorts through a tree of Debian binary packages and creates a Packages file, used by apt(8), dselect(1), etc, to tell the user what packages are available for installation. These Packages files are the same as those found on Debian archive sites and CD-ROMs. You might use dpkg-scanpackages yourself if making a directory of local packages to install on a cluster of machines.

Note: If you want to access the generated Packages file with apt you will probably need to compress the file with bzip2(1) (generating a Packages.bz2 file) or gzip(1) (generating a Packages.gz file). apt ignores uncompressed Packages files except on local access (i.e. file:// sources).

binary-dir is the name of the tree of the binary packages to process (for example, contrib/binary-i386). It is best to make this relative to the root of the Debian archive, because every Filename field in the new Packages file will start with this string.

override-file is the name of a file to read which contains information about how the package fits into the distribution (it can be a compressed file); see deb-override(5).

path-prefix is an optional string to be prepended to the Filename fields.

If more than one version of a package is found only the newest one is included in the output. If they have the same version and only differ in architecture only the first one found is used.

options

-t, --type type

Scan for *.type packages, instead of *.deb.

-e, --extra-override file

Scan file to find supplementary overrides (the file can be compressed). See deb-extra-override(5) for more information on its format.

-a, --arch arch

Use a pattern consisting of *_all.deb and *_arch.deb instead of scanning for all debs.

-m, --multiversion

Include all found packages in the output.

-M, --medium id-string

Add an X-Medium field containing the value id-string. This field is required if you want to generate Packages.cd files for use by the multicd access method of dselect.

-?, --help

Show the usage message and exit.

--version

Show the version and exit.

diagnostics

dpkg-scanpackages outputs the usual self-explanatory errors. It also warns about packages that are in the wrong subdirectory, are duplicated, have a Filename field in their control file, are missing from the override file, or have maintainer substitutions which do not take effect.


see also

dpkg , dselect, deb-override, deb-extra-override, dpkg-scansources .

How can this site be more helpful to YOU ?


give  feedback