On 2003-11-10 11:15:26 -0500, David Z Maze wrote: > dpkg does *check* dependencies, it just doesn't go out of its way to > *correct* them. That is, dpkg shouldn't let you install a package if > its dependencies aren't already installed. If you never use a --force > option and your packages work, it should be pretty hard to break your > system using 'dpkg --install'.
I didn't use --force, but my system was broken by dpkg when upgrading a package (because of dependencies on the versions). You can look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=208289 > One useful alternative might be to install the package using APT (so > you pick up the dependencies), then recompile it from source and > install it using 'dpkg --install'. This won't prevent dpkg from breaking existing dependencies (see bug 208289 for an example), as upgrading a package destroys the old version. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> - 100% validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des Jeux Mathématiques et Logiques, TETRHEX, etc. Work: CR INRIA - computer arithmetic / SPACES project at LORIA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
