Am Montag, den 09.03.2009, 10:06 +0100 schrieb Christian Faulhammer: > Hi, > > Daniel Pielmeier <daniel.pielme...@googlemail.com>: > > > 2009/3/9 Christian Faulhammer <fa...@gentoo.org>: > > > > > > I don't know if there is a bug somewhere (I did not find one), but > > > what about having the possibility to ask for one out many USE flags > > > of a dependency. For example app-misc/gramps needs dev-lang/python > > > with USE=berkdb or USE=sqlite, but Portage won't tell the user that > > > he can enable one but always asks for the first in the || () string. > > > > > > > || ( dev-lang/python[berkdb] dev-lang/python[sqlite] ) > > That's the solution currently and not the optimum. > > > The only way I found to get around this is to recompile python with > > the new use flags first. Afterwards dependency calculation succeeds. >
Correctly you should probably add a berkdb or sqlite USE flag to gramps and then do: sqlite? ( dev-lang/python[sqlite] ) !sqlite? ( dev-lang/python[berkdb] ) Because if the user currently installs gramps and has dev-lang/python[sqlite] and then later decides to reinstall dev-lang/python with USE=-sqlite, everything's fine from a package managers view as long as dev-lang/python has at least USE=berkdb, but the user looses the data in gramps. Well, even then it's not safe since it's python and gramps may offer berkdb as a storage backend even if USE=sqlite, so you should patch gramps to blend out what's not available from a dependency perspective...
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
