Bug#683859: [Aptitude-devel] Bug#683859: closed by Daniel Hartwig mand...@gmail.com (Re: Bug#683859: aptitude: APT::Get::Build-Dep-Automatic is not honored)
Aptitude provides for tracking sets of packages: # aptitude --add-user-tag foo-builddep build-dep foo I had no idea, thanks for making me aware of this! It seems like a much better solution. I'll definitely start using it. Very useful feature but I don't think it gets a lot of exposure. [then, after make foo] # aptitude --remove-user-tag foo-builddep '?user-tag(foo-builddep)' Did you mean to add an unmarkauto to this command? No, actually it should have 'remove' which I missed. The build deps are not marked auto by the first command. The second should have been: # aptitude --remove-user-tag foo-builddep remove '?user-tag(foo-builddep)'
Bug#683859: [Aptitude-devel] Bug#683859: closed by Daniel Hartwig mand...@gmail.com (Re: Bug#683859: aptitude: APT::Get::Build-Dep-Automatic is not honored)
Excerpts from Daniel Hartwig's message of Sun Aug 05 02:41:30 -0700 2012: [then, after make foo] # aptitude --remove-user-tag foo-builddep '?user-tag(foo-builddep)' Did you mean to add an unmarkauto to this command? No, actually it should have 'remove' which I missed. The build deps are not marked auto by the first command. The second should have been: # aptitude --remove-user-tag foo-builddep remove '?user-tag(foo-builddep)' Oh, right. Actually, I meant markauto, which may be better, in case something else has depended upon a foo-builddep package in the meantime. Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683859: closed by Daniel Hartwig mand...@gmail.com (Re: Bug#683859: aptitude: APT::Get::Build-Dep-Automatic is not honored)
On 5 August 2012 22:08, Andrew Pimlott and...@pimlott.net wrote: Excerpts from Daniel Hartwig's message of Sun Aug 05 02:41:30 -0700 2012: [then, after make foo] # aptitude --remove-user-tag foo-builddep '?user-tag(foo-builddep)' Did you mean to add an unmarkauto to this command? No, actually it should have 'remove' which I missed. The build deps are not marked auto by the first command. The second should have been: # aptitude --remove-user-tag foo-builddep remove '?user-tag(foo-builddep)' Oh, right. Actually, I meant markauto, which may be better, in case something else has depended upon a foo-builddep package in the meantime. Andrew An even better choice. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683859: aptitude: APT::Get::Build-Dep-Automatic is not honored
Package: aptitude Version: 0.6.8-1 Severity: normal Dear Maintainer, The apt-get build-dep command honors the APT::Get::Build-Dep-Automatic option (to mark installed packages as automatically installed). The aptitude build-dep command does not honor this option. It would be less confusing if both would honor this option. Andrew -- Package-specific info: Terminal: xterm $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.6.8 compiled at Jun 9 2012 10:02:58 Compiler: g++ 4.7.0 Compiled against: apt version 4.12.0 NCurses version 5.9 libsigc++ version: 2.2.10 Ept support enabled. Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20110404 cwidget version: 0.5.16 Apt version: 4.12.0 aptitude linkage: linux-vdso.so.1 = (0x7fff9e7ff000) libapt-pkg.so.4.12 = /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 (0x7f039a89e000) libncursesw.so.5 = /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7f039a66e000) libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f039a444000) libsigc-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7f039a23f000) libcwidget.so.3 = /usr/lib/libcwidget.so.3 (0x7f0399f3f000) libept.so.1.0.5.4.12 = /usr/lib/libept.so.1.0.5.4.12 (0x7f0399c9e000) libxapian.so.22 = /usr/lib/libxapian.so.22 (0x7f03998b9000) libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f03996a2000) libsqlite3.so.0 = /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7f03993f6000) libboost_iostreams.so.1.49.0 = /usr/lib/libboost_iostreams.so.1.49.0 (0x7f03991dd000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f0398fc1000) libstdc++.so.6 = /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f0398cb9000) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f0398a37000) libgcc_s.so.1 = /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f0398821000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f0398499000) libutil.so.1 = /lib/x86_64-linux-gnu/libutil.so.1 (0x7f0398296000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0398092000) libbz2.so.1.0 = /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7f0397e81000) libuuid.so.1 = /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f0397c7c000) librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f0397a73000) /lib64/ld-linux-x86-64.so.2 (0x7f039b228000) -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aptitude depends on: ii aptitude-common 0.6.8-1 ii libapt-pkg4.120.9.7.2 ii libboost-iostreams1.49.0 1.49.0-3.1 ii libc6 2.13-33 ii libcwidget3 0.5.16-3.4 ii libept1.4.12 1.0.9 ii libgcc1 1:4.7.1-2 ii libncursesw5 5.9-10 ii libsigc++-2.0-0c2a2.2.10-0.2 ii libsqlite3-0 3.7.13-1 ii libstdc++64.7.1-2 ii libtinfo5 5.9-10 ii libxapian22 1.2.12-1 ii zlib1g1:1.2.7.dfsg-13 Versions of packages aptitude recommends: ii apt-xapian-index0.45 pn aptitude-doc-en | aptitude-doc none pn libparse-debianchangelog-perl none ii sensible-utils 0.0.7 Versions of packages aptitude suggests: pn debtags none ii tasksel 3.11 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683859: [Aptitude-devel] Bug#683859: aptitude: APT::Get::Build-Dep-Automatic is not honored
Hi Andrew, thanks for your report. Andrew Pimlott wrote: The apt-get build-dep command honors the APT::Get::Build-Dep-Automatic option (to mark installed packages as automatically installed). The aptitude build-dep command does not honor this option. It would be less confusing if both would honor this option. I'm not sure if that would work as expected, because in comparison to apt-get (which just tells the user about no more needed packages by default), aptitude automatically uninstalls by default all packages which are marked as automatically installed and which have not at least one reverse dependency installed. This means aptitude would uninstall all those packages on the next aptitude run. On the other hand, that could be a useful feature for systems with low disk space like netbooks. :-) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683859: [Aptitude-devel] Bug#683859: aptitude: APT::Get::Build-Dep-Automatic is not honored
Excerpts from Axel Beckert's message of Sat Aug 04 14:51:35 -0700 2012: Andrew Pimlott wrote: The apt-get build-dep command honors the APT::Get::Build-Dep-Automatic option (to mark installed packages as automatically installed). The aptitude build-dep command does not honor this option. It would be less confusing if both would honor this option. I'm not sure if that would work as expected, because in comparison to apt-get (which just tells the user about no more needed packages by default), aptitude automatically uninstalls by default all packages which are marked as automatically installed and which have not at least one reverse dependency installed. This means aptitude would uninstall all those packages on the next aptitude run. I agree this may be less than ideal (a way to hold off the automatic uninstalls until ready would be nice), but it is still very useful: 1. Often you only want the build-deps for the duration of a build, so the next run of aptitude is the right time to uninstall. 2. aptitude won't automatically uninstall packages at the command line (except in the case you explicitly remove packages that allow others to be uninstalled). If you work mostly at the command line, there is no problem. (Except that the autoremove command is not there, as per my other bug, so you need to enter the UI for that.) 3. In the UI, you can hold off the uninstalls by installing with the 'I' command. So there would still be a lot of value for me! However, your point might argue for making it a different option, instead of reusing APT::Get::Build-Dep-Automatic. Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683859: closed by Daniel Hartwig mand...@gmail.com (Re: Bug#683859: aptitude: APT::Get::Build-Dep-Automatic is not honored)
Excerpts from owner's message of Sat Aug 04 18:15:03 -0700 2012: On 5 August 2012 06:49, Andrew Pimlott and...@pimlott.net wrote: (a way to hold off the automatic uninstalls until ready would be nice), Such an option exists: Aptitude::Delete-Unused. Fair. 1. Often you only want the build-deps for the duration of a build, so the next run of aptitude is the right time to uninstall. Build-Dep-Automatic is a hack used by apt-get because it lacks a better means of tracking sets of packages. Auto-installed is not intended for temporary installs but tracking packages which are installed only as dependencies of another. Aptitude provides for tracking sets of packages: # aptitude --add-user-tag foo-builddep build-dep foo I had no idea, thanks for making me aware of this! It seems like a much better solution. I'll definitely start using it. [then, after make foo] # aptitude --remove-user-tag foo-builddep '?user-tag(foo-builddep)' Did you mean to add an unmarkauto to this command? Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
