From: Ricardo Wurmus <rekado@elephly.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: After installing Java, what should I set JAVA_HOME to?
Date: Thu, 01 Dec 2016 14:07:37 +0100 [thread overview]
Message-ID: <87zikfdch2.fsf@elephly.net> (raw)
In-Reply-To: <87mvggxugq.fsf@gmail.com>
Chris Marusich <cmmarusich@gmail.com> writes:
> Radoslav Petrov <more@edno.moe> writes:
>
>> About a proper fix: IMO iced3 JDK Guix definition needs to process
>> "java.security" file for the SunPKCS11 provider to override the
>> JAVA_HOME definition with the file in the current version/dir/instance
>> of the Guix package (I'm not sure for the correct term). But this have
>> to be done on each update/upgrade of NSS package. So I'm not so sure
>> about the proper way to fix this packaging problem.
>
> This sounds right to me. If I'm hearing you correctly, there is a
> configuration file in the output of the icedtea package which needs to
> be updated whenever the nss package is updated. I believe the correct
> way to accomplish that is to use "static composition" or "late static
> composition" [1]. I'm sure a convenient mechanism for this exists in
> Guix, but since I haven't done it myself, I'm not sure of the details.
>
> [1] See section 7.1.1 in Eelco Dolstra's thesis:
> http://nixos.org/%7Eeelco/pubs/phd-thesis.pdf
We are already genarting the keystore for IcedTea. It just fails for
IcedTea 3, which is why it’s disabled there. IcedTea 2 should work just
fine.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
http://elephly.net
next prev parent reply other threads:[~2016-12-01 13:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 18:48 After installing Java, what should I set JAVA_HOME to? Radoslav Petrov
2016-12-01 2:18 ` Chris Marusich
2016-12-01 13:06 ` Ludovic Courtès
2016-12-01 13:07 ` Ricardo Wurmus [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-02 4:38 Zachary Kanfer
2016-11-02 6:18 ` Chris Marusich
2016-11-08 4:20 ` Zachary Kanfer
2016-11-08 12:31 ` Ludovic Courtès
2016-11-08 15:15 ` Ricardo Wurmus
2016-11-09 7:01 ` Chris Marusich
2016-11-09 21:22 ` Hartmut Goebel
2016-11-28 5:15 ` Zachary Kanfer
2016-11-28 8:45 ` Ricardo Wurmus
2016-11-30 22:01 ` zloster
2016-12-01 8:59 ` Ricardo Wurmus
2016-11-28 9:59 ` Ludovic Courtès
2016-11-28 17:08 ` Hartmut Goebel
2016-11-29 2:34 ` Chris Marusich
2016-11-08 15:13 ` Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zikfdch2.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=cmmarusich@gmail.com \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).