From: Maxime Devos <maximedevos@telenet.be>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Julien Lepiller <julien@lepiller.eu>,
Mark H Weaver <mhw@netris.org>
Cc: 58591@debbugs.gnu.org
Subject: bug#58591: Java packages do not appear to keep a reference to their inputs
Date: Tue, 18 Oct 2022 09:01:15 +0200 [thread overview]
Message-ID: <f23e32f8-aba2-a9b7-db69-886dfb945dcb@telenet.be> (raw)
In-Reply-To: <87edv5yhlp.fsf@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 461 bytes --]
On 18-10-2022 04:45, Maxim Cournoyer wrote:
> [...] setting CLASSPATH outside of the build systems, so even if we propagate
> Java things, I don't see how it'd find them in a profile.
FWIW, when I used java things in Guix, I manually did
CLASSPATH=$GUIX_ENVIRONMENT/... or the CLI equivalent (some option
argument of 'java').
Some more automatisation, e.g. in the form of search paths as you
propose, would be nice though.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-10-18 7:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 21:04 bug#58591: Java packages do not appear to keep a reference to their inputs Maxim Cournoyer
2022-10-17 22:03 ` Julien Lepiller
2022-10-18 1:43 ` Mark H Weaver
2022-10-18 2:45 ` Maxim Cournoyer
2022-10-18 7:01 ` Maxime Devos [this message]
2022-10-18 7:36 ` Liliana Marie Prikler
2022-10-18 13:14 ` Maxim Cournoyer
2022-10-18 13:21 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-10-18 14:17 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-10-18 14:53 ` Maxim Cournoyer
2022-10-18 14:56 ` Maxim Cournoyer
2022-10-18 15:32 ` Julien Lepiller
2022-10-18 23:25 ` Maxim Cournoyer
2022-10-18 13:29 ` Maxim Cournoyer
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=f23e32f8-aba2-a9b7-db69-886dfb945dcb@telenet.be \
--to=maximedevos@telenet.be \
--cc=58591@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=maxim.cournoyer@gmail.com \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.