FS#13364 - Package organization by repository

Attached to Project: Pacman
Opened by Fabiano Furtado (fusca) - Wednesday, 18 February 2009, 17:58 GMT
Last edited by Allan McRae (Allan) - Sunday, 22 April 2012, 11:49 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 3.2.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Summary and Info:

The pacman is a great packages manager (the best, I think), but suffers in some aspects, those mainly related the organization of information. I think everything starts after `pacman -Su` that shows the packages to be upgraded so disorganized in screen. To organize the mess, I suggest:

1) Organize the presentation of the packages to be installed by repository and show them in alphabetical order;

2) Include the parameter (maybe "-e" ??) to update only packages from repository X (example: pacman -Syue extra ====> the "-r" parameter already exists and can not be used anymore! );

Note: It is clear that if there is dependency between packages in different repositories, the pacman should automatically force the download of the package from another repository that was not specified in parameter "-e".

===========================================================================

Steps to Reproduce:

$ pacman -Syu

Before implementation:

...
Target (5): pkg_a, pkg_c, pkg_b, pkg_z, pkg_d
...

After implementation:

...
Target (5):
* core(2): pkg_a, pkg_d
* extra (2): pkg_b, pkg_c
* community (1): pkg_z
...



Sorry about my english.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 22 April 2012, 11:49 GMT
Reason for closing:  Implemented
Additional comments about closing:  VerbosePkgLists shows this information
Comment by Allan McRae (Allan) - Sunday, 22 April 2012, 11:48 GMT
Repo is shown when using VerbosePkgLists.

Loading...