From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: jetbrains-jdk-bin: update to 11.0.6b795.3.
Date: Fri, 27 Mar 2020 10:03:40 +0100 [thread overview]
Message-ID: <20200327090340.EfRi8Ah2mx4PHy_5VX4ZX270H4eyH1wXmpDnNuDannI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20384@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
New comment by Piraty on void-packages repository
https://github.com/void-linux/void-packages/pull/20384#issuecomment-604890450
Comment:
I haven't used any of these IDEs to assess possible side-effects of only a launcher script for the GUI providing the required XXX_JDK var, compared to a global env var that can possibly be used by cli tools of those IDEs (shipping launcher scripts for them as well is overkill!).
To make IDE packages independent, I suggest each of them brings a file like this to /etc/profile.d
```
export XXX_JDK="$IDEA_JDK"
```
named so that they are sourced after the JDK's one (I'm not sure you can rely on correctly sorted files though, sourcing the JDK's file to obtain its vars might be another option)
next prev parent reply other threads:[~2020-03-27 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20384@inbox.vuxu.org>
2020-03-26 20:00 ` 2asoft
2020-03-26 20:06 ` Chocimier
2020-03-26 20:18 ` 2asoft
2020-03-27 9:00 ` Piraty
2020-03-27 9:01 ` Piraty
2020-03-27 9:03 ` Piraty [this message]
2020-03-28 3:54 ` 2asoft
2020-03-28 13:50 ` Piraty
2020-03-30 19:38 ` [PR PATCH] [Merged]: " Chocimier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200327090340.EfRi8Ah2mx4PHy_5VX4ZX270H4eyH1wXmpDnNuDannI@z \
--to=piraty@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).