Arch Linux User Repository

PyCharm EAP without extra qualification is synonymous with the Professional version, as per JetBrains’s own usage. And JetBrains does not even provide a download webpage for the Community version. Since the Professional version is the default, there is no need to qualify the name, and only the non-default version needs to be qualified. This is analogous to how Python packages were handled before Python 2's EOL. Before the EOL, the Python 3 package was simply referred to as 'python', while the older version was qualified as 'python2' to distinguish it as the non-default version.

name has been used since 2011. I don't think changing the name of such long-established package is a good idea unless there's compelling benefit.

I disagree with this statement. The package naming should be consistent. Distributions sometimes change the packages name as needed.

It would require users to adapt to a new naming convention for a package that essentially remains the same, introducing unnecessary complications.

Just a simple example, all KDE packages were renamed to the packages with "5" a the end, when the plasma 6 beta appeared. For example, analitza -> analitza5.

A change in the package name after over a decade could disrupt automated scripts, dependencies, and user familiarity.

What are you about exactly? The automated scripts that build the aur package? Even there is no any dependent package.
Regarding the thing that you want this to remain searchable for those who search "pycharm-eap", you can add it to the "replaces" array (not to the "provides"). See https://wiki.archlinux.org/title/PKGBUILD.

This nomenclature suggests that the EAP version inherently pertains to the Professional edition

This is not obvious. This is also a reason why I suggest the rename.

making the addition of 'professional' in the package name redundant.

Actually, this oppositely made me unsure about this package when I was selecting the package to install. And we need to differentiate with pycharm-community-eap, and also for consistency.

Yeah, I see you added "Professional Edition" to the description, but really, please rename also the package. The history and the comments will remain (you just submit a merge request).

@Ashark this package name has been used since 2011. I don't think changing the name of such long-established package is a good idea unless there's compelling benefit. A change in the package name after over a decade could disrupt automated scripts, dependencies, and user familiarity. It would require users to adapt to a new naming convention for a package that essentially remains the same, introducing unnecessary complications.

Like I mentioned before, JetBrains uniformly refers to PyCharm EAP without specifying 'Professional' anywhere on their official website. This nomenclature suggests that the EAP version inherently pertains to the Professional edition, making the addition of 'professional' in the package name redundant.

Why this packagebase does not provide a jre package?

@qft Thanks for maintaining. Can you please rename the package as "pycharm-professional-eap", to indicate that this package edition - to keep it consistent with other aur packages and to differ from pycharm-community-eap in aur.

Sorry for the confusion, the checksum has been corrected.

Running into a checksum error:

==> Validating source files with sha256sums...
    pycharm-professional-233.11799.20.tar.gz ... Passed
    pycharm-eap.desktop ... FAILED
==> ERROR: One or more files did not pass the validity check!
-> error making: pycharm-eap-exit status 1
-> Failed to install the following packages. Manual intervention is required:
pycharm-eap - exit status 1

Looks like pycharm-eap.desktop has a different checksum:

❯ sha256sum pycharm-eap.desktop 
7801ea1379c4c183efeb78ec8d2f67bc30741548410fa51b9f4827b0188da4b2  pycharm-eap.desktop

there is no reference made for the community edition

Your package is actually a Professional edition. See this screenshot: https://ibb.co/6Rx0956. There is a Community EAP version (of the same build number) provided by pycharm-community-eap package. JetBrains use "PY" for professional edition, and "PC" for community edition. Also, they use squared icon for community and angled icon for professional (the same applies to IntelliJ Idea).

_eap variable is used because this package uses the stable version of PyCharm when the EAP period is not active.

In such period I think your package should stay at the last provided eap version. See how it is made for https://aur.archlinux.org/packages/davinci-resolve-beta. When there is no beta, the stable version actually has a more recent version number.

I will replace it with the version

Thanks.

@Ashark, on JetBrains webpage for PyCharm EAP (https://www.jetbrains.com/pycharm/nextversion/), there is no reference made for the community edition. The webpage provides download link for ONE edition only, which is the edition used by this package.

_eap variable is used because this package uses the stable version of PyCharm when the EAP period is not active.

The mixed use of tab and space in PKGBUILD will be fixed in the next release. The desktop file was never changed since the initial version in 2015. I will replace it with the version provided by JetBrains.