I fear the deprecation of so many portability related infobits in creating/maintaining CLI database entries will de-sensitize users to the need to actively look for the system traces they may carry -- after all, there's nothing preventing CLI tools from incurring in the same bad practices of some GUI development.
I have an entire directory full of CLIs (just like I have another directory full of portable GUIs) that I have collected over the years. I don't remember ever having to deal with portability issues. The main issue I have had to deal with is not being able to run some of them as I migrated upwards, but even that is quite rare.
I would suggest excluding CLIs that are 1) not portable 2) adware from the DB. The "stealth" field (discussed below) will hopefully help take care of the "system traces" bit.
NO, NO, NO, NO, NO, NO, NO and NO
From the very beginning I strongly believed that CLI DB should be exactly like the regular DB but CLI
But with the obvious connivance of others, it turned into indistinct crap
Now you want to make it even more indistinct crap
Nobody need such "DB", absolutely nobody
Haha! OK, OK. If you let me remove the icon and screenshot, maybe that will give enough visual cues to differentiate between GUIs and CLIs, which is what's bothering me now. When I look at the page, short of either looking at the URL or inferring by the app names, I can't tell whether I am on the GUI or CLI site at a glance.
Some of the points are to roll back features introduced that I'm pretty sure you were against...
With Writes settings to/Path portability, they're maybe okay to remove? An outlier that comes to mind is youtube-dl's config file which, although optional and not necessary to use the program, is nevertheless expected to be in a fixed, non-portable location (the root user directory) unless the user inserts a different config path into every command they use with the program (see: its topic on this forum). Maybe others have examples of CLI programs writing/expecting settings outside the application dir.
Exactly. I have never come across any problems with CLI portability. Settings are either supplied via command line or stored in a text-based settings file somewhere, and the latter could be easily archived and migrated to a new system. Not so for the Windows registry.
Stealth is probably a field worth keeping since some programs do create files/directories (automatically) outside of the application/working/temp directories (eg: youtube-dl which stores cache files in the root user directory). That said, by-and-large CLI programs ime tend to behave as expected in terms of file creation locations.
I think you've got a point here. Noted with thanks!