Peter Humphrey <peter <at>> writes:

> On Sunday 29 March 2015 20:12:45 Alan McKinnon wrote:

> > grep -ir qt /etc/portage
grep qt /etc/portage/package.use | wc -l =11

dev-qt/qt-creator       android autotools cmake python 
dev-qt/qtgui            qt3support
>=dev-qt/qtsql-4.8.5 qt3support
>=dev-qt/qtcore-4.8.5-r1 qt3support
# required by dev-qt/qtcore-4.8.5-r1[qt3support]
>=dev-qt/qtgui-4.8.5-r1 qt3support
# required by dev-qt/qtopengl-4.8.5
>=dev-qt/qtgui-4.8.5-r2 -qt3support
# required by dev-qt/qt3support-4.8.5
>=dev-qt/qtgui-4.8.5-r2 qt3support
# required by dev-qt/qtwebkit-4.8.5[gstreamer]

# grep -ir qt /etc/portage | wc -l  =86

# eselect profile list
Available profile symlink targets:
  [1]   default/linux/amd64/13.0 *

So I am multilib? How/where do I tell, as one reader posted
that the profile is not where we designate if we are multilib
or not (news to me). I am open to edumacation on this aspect.

> and help them remove all cruft that's getting in the way of a clean upgrade

I just ran a 'depclean' a few days ago. Dozens of my java hacks (overlays)
and such got cleaned out and my apache-spark ebuild (hack) does not compile
anymore. No big deal, I get to spend another day learning all the neat
things I do not know about maven......

I Did not even know a cleanup was needed but 'eix-test-obsolete' 
broke me down and kicked me in the teeth. I've got a lot to clean up:

eix-test-obsolete | wc -l =209

emerge -uDNvp world | wc -l =111
emerge -uDNvp world : 
Total: 98 packages (2 upgrades, 2 new, 2 in new slots, 92 reinstalls, 3

All I have done so far is run emerge --sync. I previously sync'd up on
28mar2015 before that. I do not run KDE, I use lxde + lots of java (hacks)
I refer to 'java(hacks)' because it is mostly a kludge of
old portage packages and overlays.

I have automask automated via make.conf.
EMERGE_DEFAULT_OPTS="--with-bdeps y --autounmask-write y"

 But  before I follow the  path of others:

cat package.use | wc -l   =314

package.use via automask is getting a bit out of hand, already.
Somehow, I do not feel good about the devs solution is to 
munge up something I have already been abusing. So, does
'eix-test-obsolete' have some automated option to clean up
package.use? I think I need to do this before applying
the latest (dev_inspired) kludge to my main workstation....?

Maybe I should BE the chicken that I am, and wait a few days
for others to flush this out a bit more? It's already been a
hell(o)Monday for me..............

On a brighter note, I do feel good that my instincts on kludging
up a gentoo system, seem to be tracking the devs, quite nicely....

Guidance, humor and spankings are all welcome.....


Reply via email to