Arch Linux User Repository

@rdoursenaud > 2348 _is_ the stable release and I won't mix it with the EAP releases. But this doesn't mean that Clion EAP users don't deserve 1.1 version. Instead you propose to install up to 500MB of stable release to use both versions in parallel. Thanks, that's all I needed to know about AUR.

@Light2Yellow 2348 _is_ the stable release and I won't mix it with the EAP releases. I maintain packages on my _free_ time and I don't use or track all of them daily. Sorry if it doesn't fit your tight ass schedule!

@rdoursenaud I am just following Clion updates. There is 2348 build out there, about what Clion notified me. Check it on download page. There won't be any collisions between EAP and stable because of naming conventions proposed by you (or I'm missing something?). The thing is, Jetbrains just a bit polished their EAP to look like a stable release and published the update (2348 build). And yes, they were too lazy to make another download, because stable and EAP will be the same for some period of time (as they are taking a break). But that doesn't mean that users don't deserve 1.1 version. Instead you propose to install up to 500MB to use both versions in parallel. And if I don't wan't to? My code couldn't be eaten just because it lies totally in git. Also, I haven't seen any crashes ever. To sum up, this is an EAP version, and there is a EAP update from 2347 to 2348 (to 1.1, if this sounds better). I changed the sequence of two lines because there is only one download now for EAP and stable. It seems that you don't use EAP version at all. On a previous release I waited for a few days before flagging (same thing now) but it seems you don't track Jetbrains' blog closely.

The final 1.1 release is _not_ an EAP release. Please use the clion package for that! Please remember that EAP is Early Access Preview and can be below beta quality (According to JetBrains own very terms). It can eat your cat and burn your code. That's why I keep the two release tracks in separated packages (as upstream intended). This way you (and I) can have parallel installs and return to using the stable version if something breaks. You also know for sure if you're using a stable version or an EAP. If you still insist on having a single package installing EAPs and stable versions, I suggest you roll your own clion-bleeding-edge package.

Real-time PKGBUILD: http://pastebin.com/GEzwX6K9

To download the latest version change PKGBUILD: pkgbuild=141.2347.10 sha512sums=('7c8d329a6d6c3e385dc90e589deac475867dac27cf199ddbef71633a340df8d0ba4c8c97e745b45b6d59497458a911dd9cfe6f42e7e80fd735824ab70539435c')

To download the latest version change: pkgbuild=141.2347.10

Yeah thanks but no thanks. This creates a mess at managing the versioning scheme for very little benefit. If you don't agree with the release scheme, go whine upstream.

No, I won't. EAP and stable are two separate release tracks I don't plan to mix.