> May I suggest renaming muParser to muparser? I don't mind renaming, but: 1. This will happen only upon update submission. 2. Everything that depends on muParser should have their info files updated.
So, is it really worth it? > Alien Bob's package is named muparser, and package manage tools (like > slackpkgplus) work better if different packages of the same program > have the same name. It is a different repo. Until we agree on a single unified repository for Slackware packages/SlackBuilds, issues like this will exist. So, short answer is: no, I will probably not change the name. -petar _______________________________________________ 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/
