public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Nichols <nichoj@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] binary virtual machines and use flags / dependencies (X, alsa, odbc)
Date: Thu, 06 Apr 2006 21:04:12 -0500	[thread overview]
Message-ID: <4435C89C.8030900@gentoo.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Currently, all the binary virtual machines link against libraries from
X, alsa, and  unixODBC.

Currently, we handle this in a couple ways (using alsa as an example):
* Have ' alsa? ( media-libs/alsa-lib ) ' in DEPEND/RDEPEND
	In these cases, if you don't use the USE flag, you'll have shared
objects that don't have don't have all their deps filled. This prob

* Have ' alsa? ( media-libs/alsa-lib ) ' in DEPEND/RDEPEND, and remove
the libs that link against alsa libs.
	This is better, as revdep-rebuild wouldn't be unhappy about the missing
symbols. However, if you use some classes need the missing shared
library, I'm not sure what will happen. Nothing good, I'd guess.

I don't think either of these are particular ideal. I think it would
slightly better to depend on the things that the libraries needed.
Someone that _really_ doesn't want the dependencies could put them into
/etc/portage/package.provided.

Any thoughts, or perhaps other suggestions?

- - Josh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFENcic8ATTzZyw6sMRAgFxAJ4r8KtmgPpER9DU2ZuIl6HMtywO/ACeLlpS
+qIxeyDiH/hgYn4jhixRE30=
=EAHo
-----END PGP SIGNATURE-----
-- 
gentoo-java@gentoo.org mailing list



             reply	other threads:[~2006-04-07  2:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07  2:04 Joshua Nichols [this message]
2006-04-07 19:56 ` [gentoo-java] binary virtual machines and use flags / dependencies (X, alsa, odbc) William L. Thomson Jr.
2006-04-11 16:00   ` Joshua Nichols
2006-05-01 16:45     ` 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=4435C89C.8030900@gentoo.org \
    --to=nichoj@gentoo.org \
    --cc=gentoo-java@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