Package Details: pycharm-eap 2020.3.203.4449.8-1

Git Clone URL: https://aur.archlinux.org/pycharm-eap.git (read-only, click to copy)
Package Base: pycharm-eap
Description: Powerful Python and Django IDE, Early Access Program (EAP) build. Professional edition.
Upstream URL: https://www.jetbrains.com/pycharm/nextversion/
Keywords: development editor ide jetbrains python
Licenses: custom
Provides: pycharm, pycharm-professional
Submitter: vlan
Maintainer: qft
Last Packager: qft
Votes: 28
Popularity: 0.004742
First Submitted: 2011-05-06 08:33
Last Updated: 2020-10-09 21:22

Dependencies (19)

Required by (0)

Sources (2)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

qft commented on 2019-11-02 18:24

@sanerb @Kr1ss Thank you for pointing this out and the change in pycharm-community-eap.

Kr1ss commented on 2019-11-01 18:55

Never mind @qft, I'm about to rename the starter link of pycharm-community-eap to /usr/bin/pycharm-ce, to prevent that conflict.

Thx @sanerb for pointing this out.

sanerb commented on 2019-11-01 17:58

recommend you either add a conflicts for python-community-eap or name your binary to something like pycharm-pro-eap; you're both using the same binary path (/usr/bin/pycharm-eap) and according to upstream, both should be able to be co-installed. that's the only file conflict since you install to different /opt dirs.

mitchhentges commented on 2019-01-09 17:55

Just a heads up that the current published version has the ".3" twice, causing package managers not to update.

My current version: 2018.3.183.4284.139-1 Published version: 2018.3.3.183.5153.12-1

183 > 3, so it won't upgrade :)

qft commented on 2017-10-20 17:15

The current PKGBUILD already works for both the EAP and the regular PyCharm. For example, https://download.jetbrains.com/python/pycharm-professional-172.3968.37.tar.gz and https://download.jetbrains.com/python/pycharm-professional-2017.2.3.tar.gz points to exactly the same file. Thus there is no need to specify two link formats.

As for the automatic downloading of the checksum. I find the additional wget clause to be not as clean as putting the .sha256 file inside the ${source}. However putting the .sha256 file inside ${source} requires running the makepkg command twice, which is even uglier. What's the benefit to end users if the .sha256 file is dynamically updated instead of hard-coded in the ${sha256sums} field?

danielko commented on 2017-10-20 13:59

If you don't mind could you please revert PKGBUILD to version which automatically downloaded correct SHA sum and had correct sources link for both EAP and regular PyCharm?
It was much easier to try new versions with that code.

PS. And thank you for adopting the package and adding debugger extensions compilation :)

qft commented on 2017-10-09 00:53

I have adopted this package and made some cleanups with the PKGBUILD.

lots0logs commented on 2017-08-23 02:07

====================================
----->>> MAINTAINER NEEDED! <<<-----
====================================
I haven't used this package ever since jetbrains-toolbox came out. If anyone is interested in adopting it, please do so.

deathangel908 commented on 2017-04-22 11:42

==> Starting package()...
cp: cannot stat '/tmp/pycharm-eap/src/pycharm-2017.1/*': No such file or directory
==> ERROR: A failure occurred in package().
Aborting...

# but /tmp/pycharm-eap/src/pycharm-2017.1.1/ exists
# mb it should be JUST like it's below?
# cp -R "${srcdir}/pycharm-${_pkgver}/"* "${pkgdir}/opt/${pkgname}"

lots0logs commented on 2017-03-18 22:49

Sorry about that. Its fixed now. Cheers!