I think that a description on how to add packages to the plugin, so what needs to be checked, what files need to be updated, etc... will help a lot offloading the work to the community.

Also, if the community can more easily add packages, the plugin would grow more and updates to packages would come faster.

As a suggestion I propose to include following information in the README.md on how to add packages:

• For what architecture and distro a package need to be build/compiled for (maybe even an example with one packages what steps are needed if the package is not available already compiled and needs to be compiled on the own system)
• What files need to be updated
• What needs to be tested before opening up a Merge Request

Of course this introduces the problem of verifying that a package wasn't modified from the source. For that I propose that for packages that were already found compiled, the link to the checksum could be given (so not the checksum directly but the link of where to find the checksum in combination with the package itself) to verify the package.
For packages that need to be compiled manually because they are not available in the public package lists, I propose, instead of adding the compiled package directly, which can't be easily verified, to open a Issue with the necessary commands to compile it. So that would be the commands to download the source, extract it, build and compile the package, and package it again for the plugin.

deleted: packages/6.11/python-pip-21.2.3-x86_64-1.txz

add: packages/6.11/axel-2.4-x86_64-2_slonly.txz packages/6.11/borgbackup-1.1.15-x86_64-1.txz packages/6.11/fdupes-1.51-x86_64-3_slack.txz packages/6.11/fzf-0.20.0-x86_64-3_slonly.txz packages/6.11/iotop-0.6-x86_64-1_fs.tgz packages/6.11/iperf3-3.9-x86_64-1cf.txz packages/6.11/irssi-1.2.3-x86_64-2.txz packages/6.11/jdupes-1.19.1-x86_64-1_SBo.txz packages/6.11/mediainfo-19.09-x86_64-1_SBo.txz packages/6.11/mktorrent-1.1-x86_64-1.txz packages/6.11/nload-0.7.4-x86_64-1_slack.txz packages/6.11/python-pip-21.3.1-x86_64-2.txz packages/6.11/rar-5.8.1-x86_64-1_SBo.txz packages/6.11/unrar-5.8.5-x86_64-1_SBo.txz packages/6.11/utf8proc-2.7.0-x86_64-1.txz packages/6.11/vnstat-2.1-x86_64-1.txz

Need this to update firmware on SSDs

https://manpages.ubuntu.com/manpages/focal/man1/fwupdmgr.1.html

https://www.cyberciti.biz/faq/upgrade-update-samsung-ssd-firmware/

Running Unraid 6.11.5 w/ NerdTools 2022.11.01 - Appears to be missing dependency libffi.

root@darktower:~# iotop
libffi.so.7: cannot open shared object file: No such file or directory
To run an uninstalled copy of iotop,
launch iotop.py in the top directory

https://mosh.org/

This used to be in the original NerdPack plugin but isn't in here. It's really useful when remoting into the server on a mobile connection. Please consider adding it to the plugin. Thanks!

Name: Lazydocker Source: https://github.com/jesseduffield/lazydocker Current Version 0.20.0 Description: A simple terminal UI for both docker and docker-compose, written in Go

Could someone add this? I have never built a slack package before, if someone can direct me in the right direction i will try to do it myself and make a PR. Shouldn't be too hard as lazydocker is a single binary golang application...

Can you please add bluez to the nerd-tools package.

I need bluez because I want to add a Bluetooth stick to the homeassistant docker.

Bluez was added to the old Nerd Tools and there is a issue on the other repo

https://github.com/dmacias72/unRAID-NerdPack/issues/6

https://github.com/UnRAIDES/plugin-UnRAID/issues/6