From: Vytautas Jakutis <vytautas@javy-labs.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Virtuals and Java
Date: Tue, 08 May 2007 20:01:03 +0300 [thread overview]
Message-ID: <pan.2007.05.08.17.01.01.333011@javy-labs.com> (raw)
In-Reply-To: 8fj2F-5h5-5@gated-at.bofh.it
On Sun, 29 Apr 2007 17:00:09 +0200, Petteri Räty wrote:
> We want to implement virtuals for Java at some point and for that we
> need to know the package that provides the virtual because some virtuals
> can be provided by the JDK or normal packages and this affects the JDK
> selection at build time. One option is to call into Portage to find this
> out, but of course Paludis and Pkgcore people most likely don't like
> this approach. One thing that comes to mind is to allow for virtuals to
> install files so we can install the provider information in a format
> easy for us. We need the information in format ${PN}-${SLOT} because
> that's the way we install in /usr/share. So do you think it's ok for
> virtuals to install files (we can of course call the category
> java-virtual/ too), should we call Portage code, or do you have an
> another idea?
The virtual ebuilds that utilize JAR service provider discovery mechanism
(in META-INF/services, from jdk1.4) should install its' API jars and use
virtual/ category. And those who don't - have to be patched to utilize or
have to use some special upwards compatibility layer (generate
some special metadata file and use special eclass)..?
--
Vytautas Jakutis
vytautas@javy-labs.com
--
gentoo-dev@gentoo.org mailing list
next parent reply other threads:[~2007-05-08 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8fj2F-5h5-5@gated-at.bofh.it>
2007-05-08 17:01 ` Vytautas Jakutis [this message]
2007-05-08 17:10 ` [gentoo-dev] Virtuals and Java Petteri Räty
2007-05-08 18:16 ` Vytautas Jakutis
2007-04-29 14:53 Petteri Räty
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=pan.2007.05.08.17.01.01.333011@javy-labs.com \
--to=vytautas@javy-labs.com \
--cc=gentoo-dev@lists.gentoo.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