#298734 aptitude should support sections by "server"

Package:
aptitude
Source:
aptitude
Description:
terminal-based package manager
Submitter:
Michelle Konzack
Date:
2015-07-26 15:09:07 UTC
Severity:
wishlist
#298734#5
Date:
2005-03-09 16:33:29 UTC
From:
To:
Error description:

I have more then 20 Servers in my /etc/apt/sources.list and I like
to see aptitude seperating the menu by servers like:

#298734#12
Date:
2011-07-13 15:58:30 UTC
From:
To:
tags 298734 + patch
block 603269 by 298734
thanks

Attached patch contains a group policy named `site' for grouping
packages according to their origin site (server).

- origin site is obtained from PkgFileIterator::Site()
- packages available from multiple sites appear *once* under each
---[Example] sources.list: # Will provide 3 distinct versions of iceweasel. deb http://ftp.au.debian.org/debian squeeze main deb http://ftp.au.debian.org/debian sid main deb http://mozilla.debian.net/ experimental iceweasel-beta package view: # With group policy "status,site" and view limit "^iceweasel". --\ Not Installed Packages (91) --\ ftp.au.debian.org (89) p U iceweasel p U iceweasel-dbg [...] --\ mozilla.debian.net (2) p U iceweasel p U iceweasel-dbg --- apt_preferences refers to this data using the keyword `origin', however, I have decided to use `site' for the group policy as I intend to now work on an equivilent search term and `?origin' is already in use. Using the keyword `origin' for this data seems more descriptive to me. I think that the group policy could be `origin' and the search term `?origin-site', any opinions on this? With attached patch, this layout is achieved by inserting `site' before `section' in your group policy: "task,status,site,section(subdirs,passthrough),section(topdir)" Note that this request is a dupe of #244434. I consider the patch to be fairly complete, however opinions and naming suggestions are welcome. Aptitude is an excellent tool :)
#298734#25
Date:
2015-07-26 15:07:37 UTC
From:
To:
Hi,

Daniel Hartwig wrote in 2011:
[...]

Sounds good to me.

Why not just "?site"?

Looks fine to me. I though would prefer the shorter search term "?site".

		Regards, Axel