Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dpkg-name(1) [linux man page]

dpkg-name(1)							  dpkg utilities						      dpkg-name(1)

NAME
dpkg-name - rename Debian packages to full package names SYNOPSIS
dpkg-name [options] [--] files DESCRIPTION
This manual page documents the dpkg-name program which provides an easy way to rename Debian packages into their full package names. A full package name consists of <package>_<version>_<architecture>.<package_type> as specified in the control file of the package. The <version> part of the filename consists of the upstream version information optionally followed by a hyphen and the revision information. The <pack- age_type> part comes from that field if present or fallbacks to deb. OPTIONS
-a, --no-architecture The destination filename will not have the architecture information. -k, --symlink Create a symlink, instead of moving. -o, --overwrite Existing files will be overwritten if they have the same name as the destination filename. -s, --subdir [dir] Files will be moved into a subdirectory. If the directory given as argument exists the files will be moved into that directory oth- erwise the name of the target directory is extracted from the section field in the control part of the package. The target directory will be `unstable/binary-<architecture>/<section>'. If the section is not found in the control, then `no-section' is assumed, and in this case, as well as for sections `non-free' and `contrib' the target directory is `<section>/binary-<architecture>'. The section field isn't required so a lot of packages will find their way to the `no-section' area. Use this option with care, it's messy. -c, --create-dir This option can used together with the -s option. If a target directory isn't found it will be created automatically. Use this option with care. -h, --help Show the usage message and exit. -v, --version Show the version and exit. EXAMPLES
dpkg-name bar-foo.deb The file `bar-foo.deb' will be renamed to bar-foo_1.0-2_i386.deb or something similar (depending on whatever information is in the control part of `bar-foo.deb'). find /root/debian/ -name '*.deb' | xargs -n 1 dpkg-name -a All files with the extension `deb' in the directory /root/debian and its subdirectory's will be renamed by dpkg-name if required into names with no architecture information. find -name '*.deb' | xargs -n 1 dpkg-name -a -o -s -c Don't do this. Your archive will be messed up completely because a lot of packages don't come with section information. Don't do this. dpkg --build debian-tmp && dpkg-name -o -s .. debian-tmp.deb This can be used when building new packages. BUGS
Some packages don't follow the name structure <package>_<version>_<architecture>.deb. Packages renamed by dpkg-name will follow this struc- ture. Generally this will have no impact on how packages are installed by dselect(1)/ dpkg(1), but other installation tools might depend on this naming structure. SEE ALSO
deb(5), deb-control(5), dpkg(1), dpkg-deb(1), find(1), xargs(1). AUTHOR
Copyright (C) 1995,1996 Erick Branderhorst This is free software; see the GNU General Public Licence version 2 or later for copying conditions. There is NO WARRANTY. Debian Project 2008-08-18 dpkg-name(1)

Check Out this Related Man Page

dpkg-scanpackages(1)						  dpkg utilities					      dpkg-scanpackages(1)

NAME
dpkg-scanpackages - create Packages index files SYNOPSIS
dpkg-scanpackages [option...] binary-dir [override-file [path-prefix]] > 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 com- pressed 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 for- mat. -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 dupli- cated, 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(1), dselect(1), deb-override(5), deb-extra-override(5), dpkg-scansources(1). Debian Project 2012-05-07 dpkg-scanpackages(1)
Man Page