Re: [gentoo-amd64] Re: revdep broken x11-drivers/ati-drivers net-nds/openldap

[Daiajo Tibdixious]

On 1/31/07, Duncan <1i5t5.duncan@×××.net> wrote:
> "Daiajo Tibdixious" <daiajo@×××××.com> posted
> below, on  Wed, 31 Jan 2007 10:37:05 +1100:
>
> No.  I was still talking about the ATI video drivers still.  As with
> Nvidia, the driver has some open code but some closed binary-only code as
> well.  I dealt with openldap (to the limited degree I could) further down,
> below where I quoted your mention of it.

Oh, I didn't realise.

> I've had better luck with it, but that may be simply due to the fact that
> I keep up pretty closely with ~arch, updating twice a week to daily,
> keep the system generally cruft free, don't run anything binary-only (with
> a single exception, the close to a decade and a half old now 1993 original
> Master of Orion, tho at least I run it on from-source DOSBOX)

Wow.

> If you aren't using the 3D stuff on your video card anyway, you may wish
> to see if the native xorg driver will run it.

What do I have to do to run it?

> > dev-libs/cyrus-sasl-2.1.22-r1
> > app-crypt/gnupg-1.9.21
> > net-misc/curl-7.15.1-r1
> > net-misc/openssh-4.5_p1
> > kde-base/kdebase-3.5.5-r1
> >
> All that said, there's one negative as well.  When the packages are split,
> that means most of what was the single ./configure step in the monolithic
> package now gets run many times, once for each of the split packages.

Wouldn't a configure cache work in this case? I haven't actually tried
one myself
(due to all the warnings), however within a KDE merge it should always
be the same.

> In my case, there are whole swatches of several of the monolithics that I
> don't use at all and would prefer not to have on the system (can't cause

Do you mind sharing the list of kde packates that you DO use?

> If you don't have -ldap, the profile is probably setting +ldap for you.
> Yes, I just checked, it's turned on by default in
> $PORTDIR/profiles/default-linux/amd64/2006.1/desktop in any case, so
> probably is in other similar profiles as well.

I'm using that profile. I'll try to remember to check the profile as
well as make.conf,
I'd didn't realise I would have to minus some USE flags, rather than
just omit them.

> network, I'd suggest setting -ldap in make.conf, thus overriding the
> profile.  An emerge -N world should then remerge anything that uses that
> USE flag, and hopefully kill all your dependencies on it, allowing you to

I added -ldap to my make.conf and did a full rebuild --newuse, which took most
of the day. Now, despite eix showing -ldap on kde-base/dedbase, 'equery depends'
still shows the same list (less the older version of gnupg) as above.
depclean did remove 2 more packages, but not openldap.

> unmerge it and not worry about it any more.  A quick check on the packages
> you listed says they all have the ldap USE flag, so indeed, one presumes
> toggling it off and remerging them will remove that dependency.

openssh (e.g.) also shows -ldap in eix, but still a dependent of
openldap in equery depends.

It looks to me like 'equery depends' is broken.

app-crypt/gnupg is an example of something that still has the ldap USE
flag enabled,
I've noticed some packages just blatantly ignore make.conf, and always
have certain USE enabled, which I don't understand.

> I don't like ignoring such things if I don't have to, and it shouldn't be
> necessary except on binary packages.  If you're not using openldap anyway,
> the above should remove it as a dependency, after which you can unmerge it
> and cure the problem. =8^)

After learning more about "provide_old_libs" from the bug,
and /var/log/portage/elog, I just deleted all of broken .so files, as
they were supposed to have been. revdep-rebuild is now clean.
-- 
gentoo-amd64@g.o mailing list