Bug#170480: libapt-pkg-dev: An error API with more specific codes would be nice.
Right now, apt's error API essentially tells the program
"an error occured somewhere, here's a human-readable description". This
is a nice feature, but sometimes it would be nice to be able to
distinguish particular errors. For instance, if a package list file is
missing, a frontend could automatically fetch new lists (or that
particular list) to fix the problem.
Currently the only approach is a hack: parsing the error string
returned by apt. And of course i18n will break even that. If users could
access an integer or an untranslated string token that identified the
particular error condition, that would be great.
-- System Information:
Debian Release: testing/unstable
Kernel: Linux torrent.burrows.local 2.4.19 #3 Tue Sep 24 13:11:57 EDT 2002 i686
Locale: LANG=en_US, LC_CTYPE=en_US (ignored: LC_ALL set)
Versions of packages libapt-pkg-dev depends on:
ii apt [libapt-pkg-libc6.2-3-2-3 0.5.4 Advanced front-end for dpkg
-- no debconf information
/-------------------- Daniel Burrows <firstname.lastname@example.org> -------------------\
| A conclusion is the place |
| where you got tired of thinking. |
\------- (if (not (understand-this)) (go-to http://www.schemers.org)) --------/