termux / command-not-found Goto Github PK

~ $ png
No command png found, did you mean:
 Command ping in package termux-tools
~ $

I think he should be in some other package than termux-tools.

A minimal readme should be added.

~ $ makensis
No command makensis found, did you mean:
Command makealias in package hunspell

https://github.com/termux/termux-packages/blob/master/packages/nsis/build.sh

~ $ pkg i nsis Hit:1 https://mirrors.ustc.edu.cn/termux/apt/termux-main stable InRelease Hit:2 https://mirrors.ustc.edu.cn/termux/apt/termux-games games InRelease Hit:3 https://mirrors.ustc.edu.cn/termux/apt/termux-science science InRelease Hit:4 https://mirrors.ustc.edu.cn/termux/apt/termux-x11 x11 InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree... Done Reading state information... Done nsis is already the newest version (3.08). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

~ $ cd $PREFIX/opt/nsis .../opt/nsis $ ls makensis

update-command-not-found is a utility for command-not-found to update the repositories that one has installed and synchronize them, apparently that command does not exist, has not been added or is not intended to be added?

Sorry if this is mentioned somewhere, but I failed to find anything about this, and my C++ knowledge is nil.

Try running .. for instance (it will show all commands with two characters or less). It works with ... too, but trying four periods and longer seems to not show the "did you mean" thing for some reason. This also works with other characters (e.g. try running p.thon); it reminds me of regexes.

Is this intended behavior? If so, it would be great if it was documented, I can imagine it being useful.

Currently, when we want to update the database of command-not-found, we need to bump revision in build.sh. Of course, if our updates are timely enough, this won't be a problem. But in many cases, it is not very easy to update timely. Following are three methods I thought of for this problem.

1. Implement automatic update by setting TERMUX_PKG_AUTO_UPDATE=true and customizing the termux_pkg_auto_update function. In fact, there is no need to check for version updates in termux_pkg_auto_update, just replacing TERMUX_PKG_REVISION with sed command is enough, I suppose.
2. Use Github Action and cron to automatically publish a Release/Tag, without making any changes to the source code, just increase the version number in the release/tag to "trick" our auto-update bot.
3. Use Github Action and cron to automatically generate database header files, and then publish a Release. When Action runs, it will use generate-db.js to generate header files, and then package headers, source codes and other files into a zip, and publish this zip to Github Release. build.sh is only responsible for compiling, not for generating headers.

Of the three methods listed above, I don't quite agree with the first one. Our auto-update bot runs every six hours, which is so frequent for updating command-not-found. I don't think it is needed. I think the appropriate interval between two updates should be half a month. For the second and third methods, I think both are OK, and I have no idea which one is better.

If you have any other suggestion, please feel free to post it, thanks.

Rename netcat to nmap-ncat

Originally posted by @ghost in termux/termux-packages#6921 (comment)

If one tries "nc" or "netcat", termux points to netcat, which has been renamed. Please remove or edit the suggestion.

It should be possible to do this. The cron job can be run once a week. This should also help us ensure that our repository is consistent with termux-packages git repo

ldc contains binaries from many other packages for some reason.

Not sure why this happened, need to investigate