Bug#435829: aptitude-[create|run]-state-bundle commands very annoying

[Manuel A. Fernandez Montecelo]

2016-06-08 15:38 GMT+01:00 Lennart Sorensen :
> On Tue, Jun 07, 2016 at 10:23:03PM +0100, Manuel A. Fernandez Montecelo wrote:
>> After almost a decade, things got worse over the years after this report
>> (with the binary named aptitude-curses and the now-disabled
>> aptitude-gtk, etc).  I think that it's too late to address this now.
>>
>> The solution is simple anyway, just adding the extra space, or creating
>> aliases if the same mistakes happen too often, etc.
>>
>> It's a common problem with command-line interfaces that this issues
>> arise when programs / options / files change between systems, appear in
>> newer versions, etc.  Even if we prevent this today, maybe tomorrow
>> somebody comes up with aptitude-on-steroids and "breaks" things again.
>>
>> So closing the bug now.
>
> Well I must admit my solution was to stop using aptitude entirely and
> just use apt-get.  aptitude's resolver got too noisy and annoying to
> put up with years ago so it stopped being at all useful as a tool to me.

Good solution as well, I have to admit :-)


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#435829: aptitude-[create|run]-state-bundle commands very annoying

[Lennart Sorensen]

On Tue, Jun 07, 2016 at 10:23:03PM +0100, Manuel A. Fernandez Montecelo wrote:
> After almost a decade, things got worse over the years after this report
> (with the binary named aptitude-curses and the now-disabled
> aptitude-gtk, etc).  I think that it's too late to address this now.
> 
> The solution is simple anyway, just adding the extra space, or creating
> aliases if the same mistakes happen too often, etc.
> 
> It's a common problem with command-line interfaces that this issues
> arise when programs / options / files change between systems, appear in
> newer versions, etc.  Even if we prevent this today, maybe tomorrow
> somebody comes up with aptitude-on-steroids and "breaks" things again.
> 
> So closing the bug now.

Well I must admit my solution was to stop using aptitude entirely and
just use apt-get.  aptitude's resolver got too noisy and annoying to
put up with years ago so it stopped being at all useful as a tool to me.

-- 
Len Sorensen

Bug#435829: aptitude-[create|run]-state-bundle commands very annoying

[Manuel A. Fernandez Montecelo]

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


Hi Lennart,

2007-08-03 14:45 Lennart Sorensen:

Subject: aptitude-[create|run]-state-bundle commands very annoying
Package: aptitude
Version: 0.4.6.1-1
Severity: wishlist

The new commands added to aptitude aptitude-create-state-bundle and
aptitude-run-state-bundle are really annoying.  After these were
added tab completion has become much more annoying.  Fro years I have
been able to type apticommand and get aptitude command.  Now I get
aptitudecommand unless I remember to hit a space after tab.

Given aptitude-create-state-bundle/aptitude-run-state-bundle appear to
be only for debug purposes, could they be moved to /usr/lib/aptitude or
/usr/share/aptitude so that when someone wants to do a debug state save,
they just have to type the whole path to the script.  Many other
packages put rarely needed scripts in such a place to avoid poluting the
normal PATH environment.


After almost a decade, things got worse over the years after this report
(with the binary named aptitude-curses and the now-disabled
aptitude-gtk, etc).  I think that it's too late to address this now.

The solution is simple anyway, just adding the extra space, or creating
aliases if the same mistakes happen too often, etc.

It's a common problem with command-line interfaces that this issues
arise when programs / options / files change between systems, appear in
newer versions, etc.  Even if we prevent this today, maybe tomorrow
somebody comes up with aptitude-on-steroids and "breaks" things again.

So closing the bug now.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#435829: aptitude-[create|run]-state-bundle commands very annoying

[Lennart Sorensen]

Subject: aptitude-[create|run]-state-bundle commands very annoying
Package: aptitude
Version: 0.4.6.1-1
Severity: wishlist

The new commands added to aptitude aptitude-create-state-bundle and
aptitude-run-state-bundle are really annoying.  After these were
added tab completion has become much more annoying.  Fro years I have
been able to type aptitabcommand and get aptitude command.  Now I get
aptitudecommand unless I remember to hit a space after tab.

Given aptitude-create-state-bundle/aptitude-run-state-bundle appear to
be only for debug purposes, could they be moved to /usr/lib/aptitude or
/usr/share/aptitude so that when someone wants to do a debug state save,
they just have to type the whole path to the script.  Many other
packages put rarely needed scripts in such a place to avoid poluting the
normal PATH environment.

-- System Information:
Debian Release: lenny/sid
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 
'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-1-k7 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.6-6 0.7.6  Advanced front-end for dpkg
ii  libc6 2.6-5  GNU C Library: Shared libraries
ii  libgcc1   1:4.2.1-1  GCC support library
ii  libncursesw5  5.6+20070716-1 Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a2.0.17-2   type-safe Signal Framework for C++
ii  libstdc++64.2.1-1The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
ii  aptitude-doc-fr [aptitude-doc 0.4.6.1-1  French manual for aptitude, a term
ii  libparse-debianchangelog-perl 1.1-1  parse Debian changelogs and output

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]