| 1 |
Am Montag, den 09.03.2009, 10:06 +0100 schrieb Christian Faulhammer: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> Daniel Pielmeier <daniel.pielmeier@××××××××××.com>: |
| 5 |
> |
| 6 |
> > 2009/3/9 Christian Faulhammer <fauli@g.o>: |
| 7 |
> > > |
| 8 |
> > > I don't know if there is a bug somewhere (I did not find one), but |
| 9 |
> > > what about having the possibility to ask for one out many USE flags |
| 10 |
> > > of a dependency. For example app-misc/gramps needs dev-lang/python |
| 11 |
> > > with USE=berkdb or USE=sqlite, but Portage won't tell the user that |
| 12 |
> > > he can enable one but always asks for the first in the || () string. |
| 13 |
> > > |
| 14 |
> > |
| 15 |
> > || ( dev-lang/python[berkdb] dev-lang/python[sqlite] ) |
| 16 |
> |
| 17 |
> That's the solution currently and not the optimum. |
| 18 |
> |
| 19 |
> > The only way I found to get around this is to recompile python with |
| 20 |
> > the new use flags first. Afterwards dependency calculation succeeds. |
| 21 |
> |
| 22 |
|
| 23 |
Correctly you should probably add a berkdb or sqlite USE flag to gramps |
| 24 |
and then do: |
| 25 |
sqlite? ( dev-lang/python[sqlite] ) |
| 26 |
!sqlite? ( dev-lang/python[berkdb] ) |
| 27 |
|
| 28 |
Because if the user currently installs gramps and has |
| 29 |
dev-lang/python[sqlite] and then later decides to reinstall |
| 30 |
dev-lang/python with USE=-sqlite, everything's fine from a package |
| 31 |
managers view as long as dev-lang/python has at least USE=berkdb, but |
| 32 |
the user looses the data in gramps. |
| 33 |
|
| 34 |
Well, even then it's not safe since it's python and gramps may offer |
| 35 |
berkdb as a storage backend even if USE=sqlite, so you should patch |
| 36 |
gramps to blend out what's not available from a dependency |
| 37 |
perspective... |
Archives