On 15/04/22 17:58, B. Watson <urch...@slackware.uk> put forth the proposition: > Please, no. This is extra work and complexity for something that > doesn't *do* anything at all (see my previous message). > Adding this won't hurt the SlackBuild (it will still work), but it > will act as a red herring, a thing that will confuse users and cause > them to think it's somehow important, and waste their time trying to > decide what option to choose. > In reality both options are the same: nothing happens to > /usr/share/mime/mime.cache at all, either way.
Yes, on thinking about it again, the command will run the next time something is installed that updates the cache anyway. -- Dave _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
