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#28434 - [pacman-contrib] Suggest better (real life?) option(s) in help message

Attached to Project: Pacman
Opened by Karol Błażewicz (karol) - Tuesday, 14 February 2012, 23:06 GMT
Last edited by Allan McRae (Allan) - Sunday, 22 April 2012, 10:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

pacman-contrib 4.0.2-2

[karol@black ~]$ pacsysclean -h
...
  -o <options>     Specify custom pacman query options (e.g., dt)
...
[karol@black ~]$ pacsysclean -o dt
error: package 'dt' was not found
[karol@black ~]$ pacsysclean -o zlib
344.00 KiB zlib

Can you actually specify multiple options?
[karol@black ~]$ pacsysclean -o zlib pacman
344.00 KiB zlib
[karol@black ~]$ pacsysclean -o zlib -o pacman
344.00 KiB zlib
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 22 April 2012, 10:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  Help output is now clearer. The rest is bikeshedding.
Comment by Karol Błażewicz (karol) - Wednesday, 15 February 2012, 03:04 GMT
'pacsysclean -o -dt' does work, but neither -i nor -s seems to be doing anything.
Comment by Eric Belanger (Snowman) - Thursday, 16 February 2012, 00:52 GMT
I sent a patch to fix the missing hyphen. You need to use the -o option with pacman options not package names. If you want to know how much space a certain package takes just use 'pacman -Qi'. Not all pacman query options affect the output, it's probably only usefull for -dt and -et.
Comment by Karol Błażewicz (karol) - Thursday, 16 February 2012, 01:33 GMT
I'm honestly at a loss what is the use case for pacsysclean. I've read the intro http://mailman.archlinux.org/pipermail/pacman-dev/2011-November/014754.html and have nothing against keeping this script, but ...
If I run 'pacman -Qdt' and I want to keep some of these packages, I change the install reason to 'explicitly installed'. All the others get removed, doesn't matter if big or small. Removing them with 'pacman -Rns' may free even more space if they have large dependencies (which won't be shown by 'pacman -Qdt').

1. 'expac "%m %n" $(pacman -Qdt) | sort -g | column -t' (and similar queries) is much faster but doesn't do KiB - MiB - GiB conversion. Yes, expac is an extra package.
2. 'pacsysclean -o pkgname' is IMHO actually useful, but you would have to change the "man page" a bit.
3. What are "custom pacman query options"? I guess you mean "that's the way you can alter the default 'pacsysclean' behaviour", but 'custom' feels out of place + as you said, there are few options that make sense.
4. "pacsysclean - Sort installed packages by decreasing installed size." - I would say it sorts by _increasing_size.
Comment by Karol Błażewicz (karol) - Friday, 02 March 2012, 20:58 GMT
With regard to point 1. from my previous comment: I was wrong, expac does have '--humansize' switch, so 'expac -H M "%m\t%n" | sort -g' gives pretty similar output to 'pacsysclean'.

Loading...