@XavierCLL -
@donny is very much correct when he says "Please don't touch the official distribution if such change doesn't fix broken functionality in Arch Linux".
Making changes from upstream that are not simply to fix bugs is simply NOT the Arch Way. Note the very first one, "Simplicity":
"Arch Linux defines simplicity as without unnecessary additions or modifications. It ships software as released by the original developers (upstream) with minimal distribution-specific (downstream) changes: patches not accepted by upstream are avoided, and Arch's downstream patches consist almost entirely of backported bug fixes that are obsoleted by the project's next release."
If you believe that your modifications are superior to how JetBrains intended to distribute their product, you are welcome to suggest upstream to them. Users installing this package expect the package to operate as JetBrains distributes it. Alternatively, if you insist on packaging them for the AUR, they should be done so as a separate AUR package (e.g. "pycharm-professional-nofonts").
Please rectify this and remove your deletion of the JetBrains-bundled fonts in this package, otherwise further action may be taken by this package's users. I can confirm breakage as my system fonts are not even populated in the editor, and now none of my lines line up properly. Further, my custom guides are gone. In a language that is entirely whitespace-driven such a python, this is a big deal. With multiple users confirming breakage for them with your change, "works for me" is absolutely not a justified response. This is why you do not make unnecessary changes from upstream, even if you deem them "improvements".
Further, this modification in a packaging context of a proprietary-licensed product may or may not constitute breach of license. I'd recommend consulting with JetBrains on this. However, it's quite clear that your users disagree with your modifications.
Pinned Comments