Your message dated Tue, 10 Nov 2015 00:04:07 +0000
with message-id <[email protected]>
and subject line Re: aptitude: more agressive autoinstalled handling
has caused the Debian Bug report #137388,
regarding aptitude: more agressive autoinstalled handling
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
137388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=137388
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.2.10-1
Severity: wishlist
I'm missing something in aptitudes autoinstalled package handling that
debfoster lets me do. I tend to install packages once-off when I'm doing
NMUs or whatever, and if I run debfoster after, it will present me with
each of the newly installed packages and ask me if I want to keep it.
It looks like aptitude assumes that anything I install manually with apt
or dpkg, or aptitude's command line was intentionally installed.
I would like a way to make the default state for any newly installed
package that I didn't explicitly pick in aptitude's ui to be idA, when I
go into the UI.
I'm not sure about command-line aptitude stuff, it maybe a switch like
--keeper to make it mark stuff as non-automatically-installed if I
install it via the aptitude command line.
This probably won't do for default behavior, but it would be very nice
for me, and would let me dump debfoster.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux silk 2.4.18 #1 Tue Feb 26 00:23:37 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6.2- 0.5.4 Advanced front-end for dpkg
ii libc6 2.2.5-3 GNU C Library: Shared libraries an
ii libncurses5 5.2.20020112a-5 Shared libraries for terminal hand
ii libsigc++0 1.0.4-2 Typesafe Signal Framework for C++
ii libstdc++2.10-glibc2.2 1:2.95.4-3 The GNU stdc++ library
--- End Message ---
--- Begin Message ---
tags 137388 + wontfix
stop
2002-03-12 03:06 Daniel Burrows:
On Fri, Mar 08, 2002 at 12:38:08PM -0500, Joey Hess <[email protected]> was
heard to say:
I'm missing something in aptitudes autoinstalled package handling that
debfoster lets me do. I tend to install packages once-off when I'm doing
NMUs or whatever, and if I run debfoster after, it will present me with
each of the newly installed packages and ask me if I want to keep it.
It looks like aptitude assumes that anything I install manually with apt
or dpkg, or aptitude's command line was intentionally installed.
It will track things that are automatically installed via its own
command line, but not via apt-get and dpkg (since it doesn't have any
way of sharing information with them)
It does now. One can markauto with apt or aptitude, and the package
will be uninstalled in the next runs, if nothing depends on them.
Another way for this very-specialised use case is to use user-tags,
present for a few years, and review such tagged packages from time to
time.
I'm not sure about command-line aptitude stuff, it maybe a switch like
--keeper to make it mark stuff as non-automatically-installed if I
install it via the aptitude command line.
I think this is based on a faulty assumption (above), so I'll skip it.
Hopefully I'll have some time next weekend to hack on aptitude.
We'll see.
13 years later, and the work on such a feature never happened.
2002-04-13 11:00 Robert Bihlmeyer:
I'm not sure about command-line aptitude stuff, it maybe a switch
like --keeper to make it mark stuff as non-automatically-installed
if I install it via the aptitude command line.
This is the default AFAIK. But what about having "--markauto" as an
option for "aptitude install"? This would mark even the explicitly
given packages as auto-installed, so they are ripe for removal later.
We can do once-off installation this way ("aptitude builddep foo" is
not possible yet, unfortunately).
This is also possible, with "aptitude install package&M" (see man page).
2002-04-13 17:13 Joey Hess:
Robert Bihlmeyer wrote:
This first sounded horrible, but on second thought this makes sense as
an option (not as default for Deb & Ian User). After all you will get
all "manually" installed packages nicely listed as ready for
uninstallation.
Hmm, actually it could make sense to present them seperately with the
default next action *not* being removal. I.e. a "Manually installed"
section akin to "New packages".
That would be fine for me as well.
So given all of these alternatives for a very specialised use-case, and
that the submitter was satisfied that this would be a good alternative,
I think that it's safe to close this now.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
