From: 2asoft <2asoft@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: jetbrains-jdk-bin: update to 11.0.6b795.3.
Date: Thu, 26 Mar 2020 21:18:34 +0100 [thread overview]
Message-ID: <20200326201834.DjLsVw6CzZXPBSkb65zE5Lhv62hCmhAhCHynr2FMTnc@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: 1339 bytes --]
New comment by 2asoft on void-packages repository
https://github.com/void-linux/void-packages/pull/20384#issuecomment-604663243
Comment:
So my preference here would actually be to edit the launch scripts for the
IDEs at package build time to use a common env var for all.
I've yet to explore this option.
I plan to eventually get all of JetBrains IDEs into Void, and I doubt they
will keep adding new ones often (maybe once every few years max?), so
rebuilding infrequently is fine IMO.
Or maybe add a separate package for that, which the IDEs also depend on.
That way JDK package doesnt need to be rebuilt. Something to consider.
On Thu, Mar 26, 2020, 13:06 Piotr <notifications@github.com> wrote:
> Jdk needs to be rebuild when new ide is added.
>
> With symlink theoretically ide need to be rebuild when jdk is installed
> into another path, but you as maintainer choose path, so no reason to
> change.
> With one variable, say, IDEA_JDK, ide use that variable on own side and
> jdk can be moved on own side.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/pull/20384#issuecomment-604657509>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAI2RAE2BG25NY5RW7YALJDRJOYVVANCNFSM4LUJJMAA>
> .
>
next prev parent reply other threads:[~2020-03-26 20:18 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 [this message]
2020-03-27 9:00 ` Piraty
2020-03-27 9:01 ` Piraty
2020-03-27 9:03 ` Piraty
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=20200326201834.DjLsVw6CzZXPBSkb65zE5Lhv62hCmhAhCHynr2FMTnc@z \
--to=2asoft@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).