#freebsd-ports
channel on Libera.Chat
IRC turned out to be extremely kind & helpful too.If I really need the update for some reason and the port is outdated, I've try to update myself and see if everything works as expected after updating some parts (usually version and sums are enough, but YMMV) then open a PR with the update and wait to see if the maintainer shows up and approve.Get in touch with the maintainer of the java/intellij port (usually via the listed e-mail address).
If they don't respond, look at the port and update it. I know this sounds scary, but it's actually not as bad as it might seem at first. There is the excellent Porter's Handbook and this community is very helpful too. The#freebsd-ports
channel onLibera.Chat
IRC turned out to be extremely kind & helpful too.
Looks like the Ultimate version is but not the Community versionI'd probably want to compare a couple port trees - one from the past (that contains java/intellij) from 2020 and the current tree (which does not have the 2020 port). Copying a port folder into /usr/ports is not a big problem (going by the logic that portsnap(8) employs). Sometimes, it may be acceptable to have an older version if it compiles and runs OK.
Going further down this line of thinking, there's a chance that the 2021 version of java/intellij just might be in the latest ports tree already (OP should verify that).
The Ports Collection is in fact using Git.I finally submitted a request in bugzilla for the update. Hopefully it gets accepted, it would be great if git were used, it seems quicker and easier.
https://docs.freebsd.org/en/books/porters-handbook/quick-porting/#porting-submitting ?I mean to say that I cannot submit a PR currently, I have to submit a bug containing the files / patch.
The Ports Collection is in fact using Git.
You do exactly the same, you use the git part and send the result in PR, take a look https://bugs.freebsd.org/bugzilla/attachment.cgi?id=228934&action=diffIt's an update, not a new port.
Did you create a PR? At the very least open one to request the port be updated. It would be nice if you could also add the patches to update the port. If the maintainer doesn't respond in two weeks it will get a maintainer time-out. And a port committer can commit the update without requiring the maintainer's approval. But if nobody creates a PR in the first place nothing is going to happen.Another year has passed and we still don't have an updated version. What can we do?
# setup ports
[ ! -e /usr/ports/.git ] && {
sudo git clone https://git.FreeBSD.org/ports.git /usr/ports
_USR_PORTS_CREATED=1
}
[ -z $_USR_PORTS_CREATED ] && sudo git -C /usr/ports pull
curl 'https://bz-attachments.freebsd.org/attachment.cgi?id=240395' -o /tmp/intellij-patch-2022.2.4 || _error "intellij-port does NOT exist"
# if already installed, remove
pkg info intellij > /dev/null 2>&1 && sudo pkg remove -y intellij
cd /usr/ports
_info "Applying patch to intellij"
sudo git apply /tmp/intellij-patch-2022.2.4
cd java/intellij
_info "Building intellij"
sudo make install
# after installed, fix the font rendering
# https://forums.freebsd.org/threads/intellij-openjdk-15-fonts-are-not-crisp.77475/#post-559577
sudo rm -f /usr/local/share/intellij/bin/idea.vmoptions
printf '%s\n' '-Dawt.useSystemAAFontSettings=on' | _write /usr/local/share/intellij/bin/idea.vmoptions
printf '%s\n' '-Dswing.aatext=true' | _write /usr/local/share/intellij/bin/idea.vmoptions
printf '%s\n' '-Dsun.java2d.xrender=true' | _write /usr/local/share/intellij/bin/idea.vmoptions
# update idea64.vmoptions
sudo gsed -i 's/^-Dsun.java2d.xrender=false/-Dsun.java2d.xrender=true/' /usr/local/share/intellij/bin/idea64.vmoptions
printf '%s\n' '-Dawt.useSystemAAFontSettings=on' | _write /usr/local/share/intellij/bin/idea64.vmoptions
printf '%s\n' '-Dswing.aatext=true' | _write /usr/local/share/intellij/bin/idea64.vmoptions
cd /usr/ports/java/intellij
sudo make clean
sudo rm -rf work
sudo git reset --hard HEAD
What exactly do you mean by that?In an unfortunate turn of events, my update was invalidated.