[Aptitude-devel] Bug#842219: mention how to clean up if one doesn't need those build-depends anymore

[Manuel A. Fernandez Montecelo]

Control: tags -1 + wontfix
Control: close -1


2016-10-27 06:04 積丹尼 Dan Jacobson:
>Package: aptitude
>Version: 0.8.3-1+b1
>Severity: wishlist
>File: /usr/share/man/man8/aptitude-curses.8.gz
>
>We read
>
>       build-depends, build-dep
>           Satisfy the build-dependencies of a package. Each package name may
>           be a source package, in which case the build dependencies of that
>           source package are installed; otherwise, binary packages are found
>           in the same way as for the "install" command, and the
>           build-dependencies of the source packages that build those binary
>           packages are satisfied.
>
>           If the command-line parameter --arch-only is present, only
>           architecture-dependent build dependencies (i.e., not
>           Build-Depends-Indep or Build-Conflicts-Indep) will be obeyed.
>
>OK but then mention what command(s) can then remove all those packages
>that got installed so that we are back at the state where we were before
>using build-depends.

Well, as explained there, the packages are installed in the same way
that all installs, it's just "resolving" which packages need to be
installed what this command brings to the table.

So the usual methods for uninstalling apply, only that one needs to
either pay attention to the screen or look at the install logs to
uninstall the installed packages.

I don't think that a special way to uninstall these dependencies will
ever be created, so closing this report as +wontfix.

(And as explained many times in other similar bug requests, installing
and uninstalling doesn't leave the system in the same state / with the
same packages, mostly because of recommends and other details like the
constantly evolving state of the repositories.)


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>