[Aptitude-devel] Bug#687888: usability: shouldn't list each arch as a separate package

Axel Beckert abe at debian.org
Mon Sep 17 10:56:46 BST 2012


Daniel Hartwig wrote:
> The current multi-arch support in aptitude has the goals of
> simplicity, compatibility with apt-utils, compatibility with the
> multi-arch specification, and not hiding details of the internal APT
> model via aggregation of packages.  As a long as this is a direct
> reflection of the model internal APT this design will remain.
> Help is certainly welcome to design and implement an alternative
> support for multi-arch as an optional addition to the current support.

Not sure if my suggestion can serve as default, but I've solved that
issue for myself already.

> > This is impractical when scrolling through the list. This gets
> > worse if more architectures are installed.
> You can limit the display (“l”) with “~r$arch” if the length bothers you.

I've set Aptitude::UI::Default-Grouping to a value starting with
"status,pattern(?architecture(foreign) => Foreign architecture, ?true ||),..."

So under "Installed Packages", "New Packages", etc. I see as first
submenu "Foreign architecture" and then just the normal view. That way
I easily keep those packages separated.

I'm sure this can be expanded to more than one foreign architecture.

		Regards, Axel
 ,''`.  |  Axel Beckert <abe at 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

More information about the Aptitude-devel mailing list