RaraRasputin
Tux's lil' helper
Joined: 04 Jun 2004
Posts: 142
Location: Germany
|
 Posted: Mon Mar 09, 2009 4:26 pm Post subject: Soprano: sesame2 useflag replaced by java useflag? |
 |
|
Hello,
I am using the kde-testing overlay.
I have installed soprano. Till version 2.2.1 it had a useflag "sesame2", since version 2.2.2. it has a new useflag "java". Do these useflags have the same semantics?
This question arose because when trying to run
nepomuk tries to pull in soprano-2.2.1 because it wants soprano emerged with USE=sesame2, whereas kdelibs-4.2.1-r1 wants >=soprano-2.1.64 and always pulls in soprano-2.2.2:
| Code: | !!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-libs/soprano:0
('ebuild', '/', 'dev-libs/soprano-2.2.1-r1', 'merge') pulled in by
dev-libs/soprano[clucene,sesame2] required by ('installed', '/', 'kde-base/nepomuk-4.2.1', 'nomerge')
(and 1 more)
('ebuild', '/', 'dev-libs/soprano-2.2.2', 'merge') pulled in by
>=dev-libs/soprano-2.1.64 required by ('installed', '/', 'kde-base/kdelibs-4.2.1-r1', 'nomerge')
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in the
dependencies of two different packages, then those packages can not be
installed simultaneously. |
Adding
| Code: | | =dev-libs/soprano-2.2.2 |
to package.mask solves this conflict, but if java and sesame2 were the same useflags, I could change the nepomuk ebuild to accept the java useflag and thus using the latest version of soprano.
-Rasputin
_________________
RaraRasputin, lover of the Russian Queen |
|
Desktop Environments
