Repository navigation
Replies: 2 comments
|
I would be nice to know in advance, indeed. I think you can insulate yourself against any adverse effects from changes, however, since it's possible to redefine both the config path and the cache path through env vars, and, as for the binaries themselves, you can rename them to whatever you like, and they seem to work just as well, going by a different name (on Linux, anyway). For instance, on my system, czkawka_cli instead goes by "czkawcli". But I suppose krocliet, or maybe just krocli, could work, too. :) |
0 replies
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
As of v12.0, Czkawka GTK is deprecated and Krokiet is the successor GUI, and the README is now Krokiet-first. At the same time, the repository is still
qarmin/czkawka, and both the core library (czkawka_core) and the CLI (czkawka_cli) keep the "czkawka" name.With the branding shifting toward Krokiet, I'd like to understand the long-term plan for the "czkawka" name:
Repository: Will it keep the
qarmin/czkawkaname, or is a rename tokrokiet(or similar) planned at some point?CLI: Once Czkawka GTK is fully retired, what happens to
czkawka_cli? Does it keep its current name, get renamed (e.g.krokiet-cli), or is it also being phased out? I'm assuming it stays as an independent MIT frontend, but I'd like to confirm.Core: Same question for the
czkawka_corecrate name — does "czkawka" remain the umbrella/project + library name while "Krokiet" is specifically the GUI brand?Not urgent — just trying to understand the intended direction before it affects packaging, scripts, and documentation on my side. Thanks!
All reactions