Skip to content

Conversation

@x0rgus
Copy link

@x0rgus x0rgus commented Jul 27, 2025

This tool provides an interactive fzf-powered TUI interface as well as traditional CLI subcommands. It replaces the now deprecated blackman tool, which is still referenced in official documentation but no longer maintained or recommended.
s2
s1

License: MIT

@x0rgus x0rgus requested a review from noptrix as a code owner July 27, 2025 22:12
@noptrix
Copy link
Contributor

noptrix commented Jul 28, 2025

@noraj @dualfade @ikstream mind giving this a quick look? seems like it has potential.

@noraj noraj self-requested a review July 28, 2025 21:31
@ikstream
Copy link
Member

I apriciate every contribution and I would really love to see blackam making a comeback. I did only a quick review, so take my feedback with that grain of salt. If I did oversee something, please point it out.

This tool, at it's current state is a wrapper around pacman. The key selling point of blackman was to build packages from source from our repo or basically any repo based on it's pkgbuild file. It had/has it's flaws, that's why it's no longer in use. This tool allows searches through pacman, installs through pacman and list categories through pacman.

I don't see the blackman replacement as it is mentioned in the description.
My main Problem with that is, that it adds complexity. Currently if user complain, that something isn't working, it's either our broken keyring, or something with the packages (either ours, or upstream). If user start using install commands through something that goes more in the direction of pamac (Manjaro) we start adding overhead to troubleshoot where the issue lies without adding to much value (from my point of view) to pacman.
I would prefer user to be able to use pacman properly, especially as most of the commands are provided on the website or the guides. I am all in for enabling user to get competent and learn new stuff. But in my opinion this wouldn't be the right way to it.

As I mentioned before, I did a quick review, so if anything is wrong, please point it out. I really appreciate the efffort you put in here, with even a man file and autocomplete commands. But from my point of view it's unfortunately in the wrong tool/direction.

@noraj
Copy link
Contributor

noraj commented Jul 30, 2025

I agree with @ikstream. In short, yes for the info about packages and search TUI, no to the install package wrapper (note it can lead to partial upgrade).

@x0rgus
Copy link
Author

x0rgus commented Jul 31, 2025

thank you for the feedback @ikstream @noraj , taking that into account, i have rewritten the tool from the ground up. It no longer functions as a pacman wrapper and instead build packages from source now. The main features, including the fzf based interactive menu to sync, browse categories, and build tools, are now fully operational. I believe this new approach is much more aligned with the project's goals and would appreciate your thoughts on this new version, i'm still working on some features like installing multiple packages, but the core features were migrated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants