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#27258 - [pacman-contrib] Display help message with 'paclist -h'.

Attached to Project: Pacman
Opened by Karol Błażewicz (karol) - Saturday, 26 November 2011, 00:49 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 07 December 2011, 16:07 GMT
Task Type Feature Request
Category Scripts & Tools
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 4.0.1
Due in Version 4.0.2
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

All the other scripts in pacman-contrib print some help when invoked with '-h' switch, but paclist follows a different convention:
[karol@black ~]$ paclist -h
[karol@black ~]$ paclist
paclist - List all packages installed from a given repo
Usage: paclist <repo>
Example: paclist testing

Some scripts display help message when invoked w/o any arguments (e.g. bacman), but then paclog-pkglist needs no arguments and 'paclog-pkglist' just runs the script. I think establishing some conventions and unifying the behavior would be nice.
This task depends upon

Closed by  Dan McGee (toofishes)
Wednesday, 07 December 2011, 16:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  commit 61ce2ca1b, thanks Lukas.
Comment by Karol Błażewicz (karol) - Saturday, 26 November 2011, 02:44 GMT
I see Allan changed the category of this feature request:
Category: Packages: Testing -> Scripts & Tools
Reported Version: [-] -> 3.5.4

The thing is, 'paclist -h' works OK in pacman-contrib 3.5.2-1, but not in pacman-contrib 4.0.1-1
Comment by Dan McGee (toofishes) - Tuesday, 29 November 2011, 22:04 GMT
  • Field changed: Reported Version (3.5.4 → 4.0.1)
"The thing is", this is not a [testing] bug at all so you filed it in the wrong project. Thanks for including the version info in the original bug report...
Comment by Karol Błażewicz (karol) - Tuesday, 29 November 2011, 22:18 GMT
While you're absolutely right that I should have included the version info in the report, the category was chosen automatically when I clicked 'Add New Bug' on http://www.archlinux.org/packages/community-testing/any/pacman-contrib/.
Comment by Lukas Fleischer (lfleischer) - Friday, 02 December 2011, 08:50 GMT
Sent a patch to pacman-dev [1].

[1] http://mailman.archlinux.org/pipermail/pacman-dev/2011-December/014815.html

Loading...