cupt_vs_apt

Langue: en

Autres versions - même langue

Version: 2010-06-14 (ubuntu - 24/10/10)

Section: 5 (Format de fichier)

Sommaire

NAME

cupt_vs_apt - overview of things Cupt and APT differ in

ADVANTAGES

Core

•
pins can be specified also by source package
•
negative pin values don't strictly prevent version to be installed
•
correctness of APT options is checked

Search

•
'search' command searches all versions of package, not policy or installed ones
•
'search' command can search case-sensitively ('--case-sensitive' switch)

Interface

•
'show' command can show release description ('--with-release-info' switch)
•
'/<distribution' and '=<version>' suffixes can be used with 'depends' and 'rdepends' commands
•
'policysrc' command
•
'shell' command

Managing packages

•
'satisfy' command is present
•
two types of multi-case problem resolvers available (see --resolver in cupt(1))
•
worker passes '--force-*' options to dpkg only when really needed, not always
•
source versions of the same binary packages can be synchronized by resolver (see option cupt::resolver::synchronize-source-versions)

Downloading

•
HTTP redirects can be followed (see acquire::http::allow-redirects in cupt(1))
•
downloading deb binary packages via debdelta(1) is supported

DISADVANTAGES

•
cdrom URI type is not handled
•
PDiffs are not supported

DIFFERENT BEHAVIOR

Configuration

•
'apt::cache::allversions' defaults to 0, not 1 as in apt-cache
•
setting 'acquire::<protocol>::[<host>::]proxy' to "`` is equivalent to setting it to ''DIRECT"
•
'gpgv::trustedkeyring' defaults to '/var/lib/cupt/trusted.gpg'
•
to prioritize compression types, use option 'cupt::update::compression-types', not 'acquire::compression-types'