cupt_vs_apt(5)
NAME
cupt_vs_apt - overview of things Cupt and APT differ in
ADVANTAGES
- Core
- o pins can be specified also by source package
- o correctness of APT options is checked
- Search
- o 'search' command searches all versions of package, not policy or
installed ones
- o 'search' command can search case-sensitively ('--case-sensitive'
switch)
- Show
- o 'show' command can show release description ('--with-release-info'
switch)
- o '/<distribution' and '=<version>' suffixes can be used with
'depends' and 'rdepends' commands
- Managing packages
- o 'satisfy' command is present
- o two types of multi-case problem resolvers available (see --resolver
in cupt(1))
- o worker passes '--force-*' options to dpkg only when really needed,
not always
- Downloading
- o LZMA-compressed index files are supported.
- o HTTP redirects can be followed (see acquire::http::allow-redirects
in cupt(1))
DISADVANTAGES
o working with source packages is not yet implemented
o translated descriptions are not yet implemented
o cdrom URI type is not handled
DIFFERENT BEHAVIOR
- Configuration
- o 'apt::cache::allversions' defaults to 0, not 1 as in apt-cache
- o to explicitly disable proxy, set
'acquire::<protocol>::[<host::]proxy' to "", not to "DIRECT"
- o 'acquire::<protocol>::[<host>::]proxy' options take precedence over
"<protocol>_proxy" shell variables
- o 'gpgv::trustedkeyring' defaults to '/var/lib/cupt/trusted.gpg'