I understand this may not be exactly how you meant your comment, but I think it's important to clarify that free/libre software can also be commercial software, and in fact must allow commercial use in order to fit the Free Software Definition. It is probably easier to make lots of money with non-freely licensed software but I think contrasting "public" code with "commercial" code muddies the terminological waters a bit.
surpador
joined 2 years ago
I feel like this is a missed opportunity to spread the good news of the many other Latin pronunciation systems, particularly the traditional English system from which we get most of the English scientific pronuciations :)
You don't need to make your own module, you really just need a package definition. This (packaging tutorial)[https://guix.gnu.org/en/blog/2018/a-packaging-tutorial-for-guix/] is a bit old but should still be helpful.
An easier method might be to clone the Guix git repo, edit the package definition in education.scm, and use (pre-inst-env)[https://guix.gnu.org/manual/en/html_node/Running-Guix-Before-It-Is-Installed.html] to install your newer version.
But if you're going to to that, you might as well just (submit a patch)[https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html] so others can benefit from the new package. If it's just a version bump, it might be as simple as bumping the version number in the definition!
"Commercial" is not the opposite of free/libre. In fact, GPL licensed software can be "taken commercial" with a guarantee that it will remain libre, whereas BSD-licensed software doesn't have those guarantees.