Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#42981 - Make "pacman -Qc" output more pretty

Attached to Project: Pacman
Opened by Evgeniy Alexeev (arcan1s) - Tuesday, 02 December 2014, 07:55 GMT
Task Type Feature Request
Category Output
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version git
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I know that a few maintainers use ChangeLog pacman feature, but I hope we will use it in the future.

I want ask to add the following feature to the formating:

1. Show information in the default pager.
2. pacman -Qc should show only the last changes whereas pacman -Qcc shows all changes.
3. Bold/color output. Version should be shown in bold (white) whereas changes are as a normal text.

Items 2 and 3 also require from us to define ChangeLog format. I think that the better way is to indicate version (with a colon may be) and next changes list in new line with asterisk at the beginning of the line, for example:

1.0.0:
* some awesome changes
* fix FS#100500
This task depends upon

Comment by Dave Reisner (falconindy) - Tuesday, 02 December 2014, 14:06 GMT
> but I hope we will use it in the future.
pacman providing this feature is orthogonal to Arch packagers actually using it. That said, why do you hope this? What does the changelog provide for Arch that we can't get out of SVN/git logs?

> * fix FS#100500
Typo?
Comment by Evgeniy Alexeev (arcan1s) - Wednesday, 03 December 2014, 01:29 GMT
As developer (or people involved to Arch development) we look at svn commit history. But for normal user it is usually easily to run a simple command and do not search required commit in our repo. Changelog feature is a very useful for rolling release distro since(BTW at least we may use commit history as a default changelog.) we have a lot of package updates per day (our bug fixes, upstream bug fixes, rebuild due to 3rdparty update, upstream update, etc), it is not clear what changes have been made in the package and SVN log is not more easy to use than local changelog stored in the package directory.


> Typo?

Nope, just an example
Comment by Dave Reisner (falconindy) - Wednesday, 03 December 2014, 19:15 GMT
> But for normal user it is usually easily to run a simple command and do not search required commit in our repo.
I'm all for helping users, but not at the cost of inconveniencing myself and all other developers. What you suggest is purely a duplication of work. If you want this to be viable, you'll have to come up with automation to ensure that it's done consistently and isn't an additional burden.

Loading...