Package: debfoster Version: 2.7-1.1 Severity: normal > I usually do this by using equivs to create an empty dummy package > called like the project name which depends on all packages the project > uses.
I don't like this solution, because whenever a package needs to be removed, even temporarily, you need to redo the equivs package. Otherwise, aptitude will want to remove all its dependencies, and you'll have to re-tag all other dependencies in debfoster. Currently I just need to remove a line in 'keepers'. Likewise, when I need to a add a single package for some reason, maybe as an exception on one system, I won't need to make yet another equivs package. Being able to comment on kept packages sounds more efficient and convenient. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debfoster depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libgc1c2 1:6.8-1.2 conservative garbage collector for Versions of packages debfoster recommends: ii apt 0.7.25.3 Advanced front-end for dpkg debfoster suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
