@fbodymechanic Your lifelong vendetta against Pamac (although noble and just I’m sure) still doesn’t quite answer my question; I’m not trying to burn or toss anything off any balcony, I don’t even have a balcony! But I thank you kindly nonetheless for your response
@tbg No, I saw that too and used the command. But the issue with that command is it shows everything under the sun; there’s “too much fluff” for the task I’m talking about. That command shows not only installed/removed/upgraded packages, but it also shows anytime a transaction was stared, any possible warning messages, it displays [ALPM-SCRIPTLET] information which I don’t need to see at all (aka all those messages you see after a kernel upgrade just to name one of them), and it displays [PACMAN] information, which shows synchronizing package lists every time you ran it, which I don’t need to see that constantly at all either. The Pamac approach is simple, straight to the point, and it can’t really get any easier than that I don’t think. The only option I can think of if there was an alias I could create that essentially runs whatever command Pamac transaction history runs and then I’d be more or less set to use that instead I believe.
should do what you’re asking - alias that as appropriate. Or a variation as you choose, of course
You could also pipe it through sort (if you want them grouped) or through less (if you want it paginated) - or into a (temporary?) text file for browsing as example of enhancements. Enjoy!
$ pacman -Qo paclog
/usr/bin/paclog is owned by pacutils 0.11.1-1
$ paclog --help
paclog - filter pacman log entries
usage: paclog [options] [filters]
options:
--config=<path> set an alternate configuration file
--root=<path> set an alternate installation root
--sysroot=<path> set an alternate installation system root
--debug enable extra debugging messages
--logfile=<path> set an alternate log file
--[no-]color color output
--pkglist list installed packages (EXPERIMENTAL)
filters:
--action=<action> show <action> entries
--after=<date> show entries after <date>
--before=<date> show entries before <date>
--caller=<name> show entries from program <name>
--commandline show command line entries
--grep=<regex> show entries matching <regex>
--package=<pkg> show entries affecting <pkg>
--warnings show notes/warnings/errors
I don’t know, maybe it’s just me, but I have always had terrible experiences with GUI installers in Linux, not just pamac, but the fedora gui installer, the ubuntu gui installer, the linux mint installer, they all suck. It is so much easier to use the command line, and you get the added bonus of feeling leet once you get used to it
Are you asking if using octopi to install pamac is popular? I would say probably not.
That being said, yes, octopi is still available in the AUR. It certainly isn’t as popular as it used to be but I wouldn’t let that influence your decision either way.
I think Garuda has octopi installed out of the box if you have one of the KDE versions. I never use it on my computer that has garuda on it, but I believe it is there nonetheless.
So - the easy answer (for now) is to insert some variation of the following in your .bashrc:
alias logrem='paclog --action=remove | less'
alias logins='paclog --action=install | less'
alias logupd='paclog --action=upgrade | less'
Of course, sorting could be inserted into those, or whatever you want - but there is simple…
EDIT:
Optional colourization version:
alias logrem='paclog --color --action=remove | less -r'
alias logins='paclog --color --action=install | less -r'
alias logupd='paclog --color --action=upgrade | less -r'
One alternative I forgot (!) to mention - a little goody that lives in the EndeavourOS repo - pahis.
This can list pacman log entries by any category, or by a package name, or all etc etc. Actually - most things you might need are covered in there somewhere
