Arch Linux User Repository

@munir0b0t: AFAIK it should take seconds, or maybe minutes. It's not actually building anything, just repackaging binaries into a pacman pkg.

I have however disabled compression of the packages in makepkg.conf because I don't use that much AUR packages so I'd rather have the speed instead of the disk usage.

Maybe the downloading is taking long?

How long does this package take to build typically? I have a decent enough system (8 cores, 8 GB RAM, 16 GB swap) and the package takes upwards of an hour to build with yay -Syu. Trying to figure out if that is expected or something's wrong with my system. Most of the time is spent compressing the package and in the rsync command.

It seems some of those tools don't handle conditional dependencies very well... I've reverted the change to JRE bundling, and added a comment on the java-runtime dependency to point users to the JetBrains documentation around using an external JRE instead.

That's a shame! I liked the way it was set up before. Oh well...

Why if the java-runtime is included, does it say on the AUR website that it still needs java-runtime? It works when compiling myself but when using yay it asks for a java-runtime.

@c02y: I got tired of people complaining it was "broken" because they couldn't read JetBrains' documentation on using an external JRE. So now, if you want to use an external JRE, you need to change a flag in the PKGBUILD instead (see the comment near the top of the file).

To be fair to users, the new native launcher doesn't automatically detect a JRE like the old shell launcher did, so it's less obvious... But using the bundled JRE is technically still optional.

There is no clion-jre package anymore, pacman/paru asks for installing a package like jdk/jdk-openjdk, but package rustrover-jre for rustrover or goland-jre for goland still exists, anyone knows what's going on?

For a usable install I'd say you need to install it like paru -S clion clion-jre clion-cmake (or yay)

clion did not start after update. The issue was for certain files there was no update made, but the new versions were saved as *.pacnew. I had to manually rename following files in /opt/clion/bin

mv clion64.vmoptions clion64.vmoptions.old
mv clion64.vmoptions.pacnew clion64.vmoptions
mv idea.properties idea.properties.old
mv idea.properties.pacnew idea.properties

maybe it would be better instead of saving new files as *.pacnew the old files should be renamed into something and the new files should be used.

You must install the clion-jre package (strongly recommended, and part of the package set in this PKGBUILD) or jre-openjdk.