I mean it is would indeed a nice addition to HaikuDepot.
btw. Is Java port now support AWT? Because Clion is write in JAVA
Normally, I would call such forum posts spam, because they simply share a link with the message “this can now be found there.”
Please, if you post something like this, include an explanation of what it is about. Not everyone knows what it is, and I tend to block such things for security reasons.
I totally agree, a few words about the application / context is more than welcome
Free for personal use <> Open Source
Sure, we could download the Linux tarball, rip out the Jars and make a package out of it. Technically, we could probably do that. But it is still a commercial product with just an opt-out for private use. Not something you could put up on the repo without first negotiating with Jetbrains.
It doesn’t use AWT, but a heavily customized version of Swing.
Maybe just use HaikuPorts
To stand on side with QTCreator, KDevelop and maybe Genio in future. This “open” possibility adds some foresight for current as well as future C/C++ dev. having modern toolkit for such task is benevolent from JetBrains team.
Bad form replying to my own post, I know.
But just out of curiosity, I downloaded the tarball and had a look. Man, that sure is a LOT of jarfiles. Porting it is going to take some Java expertise. Who did IntelliJ IDEA for us?
CLion is quite a monster, packaging at haikuports isn’t a thing I’m looking forward to as you can just grab the archive, extract and launch it.
Checked few years back:
Haikuports is for free software, not commercial software.
Shouldn’t ports be used for Ports mainly?
Haikus package management is deliberately designed to allow you to install several remote repositories, or install packages without a backing repository.
Haikuports hosts free software, if your software doesn’t roughly match this It likely does not belong in haikuports.
Nothing is stopping a commercial entity from distributing their software for Haiku, but that doesn’t mean Haiku or Haikuports has to do it for them, and in this specific case, we already have severall other free IDEs, so why bother with porting one that isn’t free?
I was goi g to say, it is just an IDE base on the InteliJ platform and I though that was able to run previously?
I have a license and so it would be quite cool for it to work.
What we have is IntelliJ IDEA Community Edition, which is a cut-down open-sourced version of the commercial product. You can see the differences here: JetBrains Products Comparison
Yes. Since OP hasn’t updated their post, here is some info for those who doesn’t like to click on outbound links to read the news.
CLion is a cross-platform IDE from JetBrains for C and C++
It used to require a paid license, but a few days ago JetBrains made it free for non-commercial use:
Last year we implemented a new licensing model for RustRover, Rider, and WebStorm, making them free for non-commercial use. We’re now extending this model to CLion. If you’re using it for non-commercial purposes, such as learning , open-source project development , content creation , or hobby development , you can now do so for free. For commercial use, our existing licensing model still applies.
One additional thing to mention, as many people here find that aspect important:
It’s important to note that, if you’re using a non-commercial license, you cannot opt out of the collection of anonymous usage statistics. We use this information to improve our products. The data we collect is exclusively that of anonymous feature usages of our IDEs. It is focused on what actions are performed and what types of functionality of the IDE are used. We do not collect any other data. This is similar to our Early Access Program (EAP) and is in compliance with our Privacy Policy.
It’s worth to mention that core (meaning regular) Haiku and HaikuPorts project committers were always able to get CLion and other JetBrains licenses for free (and without that mandatory usage statistics collection thing):
We discussed that a few years ago (here). Other than free/non-free debate, there’s an issue with redistributing the binaries which is prohibited by JetBrains EULA (though I’m not sure yet if that differs for the free non-commercial use version), and
PulkoMandy suggested a simple and elegant solution:
we can store the recipe and mark them broken so they don’t land in the repository.
That way we wouldn’t distribute HPKG, and users would download binaries directly from the JetBrains site, which they are fine with (they even mention brew cask
installation method in the official documentation).
Another option would be to create a simple downloader app (lightweight version of JetBrains Toolbox) for Haiku IDEs and publish that in HaikuPorts. It’d be free and open source, and would download CLion (potentially also other of theirs IDEs) from its original location provided by JetBrains, showing the EULA if needed. Win-win solution, but someone needs to write the app.
And the last but not least option is: GitHub - przemub/haikuports-nonfree: Unofficial non-free recipes repository for HaikuPorter
Intriguing. A bit too much work for the average user, but devs should be able to handle it and that is the kind of software we are looking at here. But the site hasn’t been updated for five years. Is przemub still around?
He’s quite active on GitHub.
There are two sides to this problem:
- the jetbrains EULA. As you mention, there are solutions to this. Another one would be to ask JetBrains for a special license to allow repackaging and redistributing.
- HaikuPorts policy. Some people here say that haikuhorts is only for free and open source software. This is not true, there are some non-free packages already. For example I maintain vlink, vbcc and vasm which have a similar “free for nh-commercial use” licence. The license is clearly tagged in each package, and if you care about using only free software, you should check that before installing things.
On the other hand, there are things that are actually excluded from haikuports: packages where the license does not allow redistribution (that is not really a haikuhorts policy, the license does not allow us to do it), and packages where no sourcecode is available. Ideally all packages would be built from sources on haikuports managed infrastructure (there are a few exceptions for packages that can’t be built on haiku currently) and reproductible (we are not doing that yet: you can re-run the build locally, but there will always be differences with the package built by the bot. So you can’t make sure that the bot is doing its job correctly, it could be compromised and used to inject malware in some package).
Currently JetBrains fails these two checks: no sourcecode, and license does not allow redistribution. Fixing these two problems (it seems unlikely) would allow packaging in haikuports, even if the license still had other non-open-source limitations (such as a non-commercial use clause).