Detecting circular dependencies

cach0rr0 · Posted: Mon Nov 30, 2009 7:55 am Post subject:

dont know what the formal/official stance on this is, but those USE flags seem excessive at first glance.

For example, you want both apache and KDE on this?
And "hardened" USE flag on a system with X and KDE?

SLBMEH · Posted: Mon Nov 30, 2009 8:32 pm Post subject:

My personal rule of thumb is the less global settings the better. Some use flags are heavily supported, others are supported fairly well for some packages, but not so much for others... that statement isn't based on anything other than my preset assumptions

but... anyhow... say you have a use flag... we'll use freetds... you happen to have the freetds libs specified to install with ~arch... it ends up breaking functionality in package a and in package b... it's something that isn't used much with package a so it's a low priority fix and might just be pushed upstream... it's something that's almost crucial for package b so they make a patch and fix it immediately... package b works fine now after you rebuild it... but package a might remain unusable for a while and you need to install a lower version in a slot or rollback your current installation of freetds...

That was a terrible example and a fairly unrealistic scenario... but i guess what i'm saying is i do the complete opposite when it comes to use flags as much so that it's almost overkill... in my make.conf i have USE="-* doc examples" and everything else is put into a file under /etc/portage/package.use/*

I hope you can figure out what I'm trying to say...
_________________
Steve - Semper Fi

amightywind · Posted: Wed Dec 09, 2009 1:28 am Post subject:

SxN,

I am having precisely the same problem. This has nothing to do with KDE or Gnome. The ebuilds seem to have mutual dependencies so one of them is broken.

amightywind · Posted: Wed Dec 09, 2009 2:14 am Post subject:

I added the following lines to /etc/portage/package.use

cach0rr0 · Posted: Wed Dec 09, 2009 8:08 am Post subject:

bah...i remember that crap when i was trying to set up openldap

I had to first emerge cyrus-sasl with USE="-ldap", then emerge openldap, then emerge cyrus-sasl with USE="ldap" (since well, I needed it)

what I can't gather is why openldap is pulled in in the first place.

Mike Hunt · Watchman Joined: 19 Jul 2009 Posts: 5287

It's actually a new cxx USE flag that was added to the desktop (and maybe to others) profile. You only need to disable it like so:

amightywind · Posted: Sun Dec 13, 2009 2:44 pm Post subject:

Nice try. The cxx flag is ancient. I congratulate you for getting openldap to emerge, but that doesn't answer the question as to why the ebuild isn't smart enough to -cxx itself if that is really what is intended. package.use should be a point of customization not a place for essential configuration.
_________________
amightywind

Mike Hunt · Watchman Joined: 19 Jul 2009 Posts: 5287

It looks like cxx was added to the default profile on Dec 03, 2009. Of course openldap never needed this, and since it causes a circle block with cyrus-sasl, why not disable it in package.use. Problem solved.

BTW, it looks like that's already been resolved in the openldap ebuild, so that block shouldn't even exist anymore.