From: Wes Gray <smiths@alumni.cse.ucsc.edu>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] KDE split ebuilds broken
Date: Fri, 23 Sep 2005 15:56:07 -0700 [thread overview]
Message-ID: <20050923225607.GA18249@beavis> (raw)
When I first upgraded to 3.4 I was unaware of the new split ebuilds,
so I just emerged normally getting (I assume) the old monolithic
ebuilds. When I finally got around to trying to use 3.4 (which was
a few months later) KDE came up with the taskbar not able to start,
and as such I couldn't see any minimized tasks. In researching I
discovered the new split ebuilds, read the "KDE split ebuilds howto",
and decided to see if using the split ebuilds would solve my problem.
So I unmerged kdebase and then emerged kdebase-meta. After doing that
not only does taskbar not work, but the pager and the clock won't run
and give me similar error messages when I start kde. The howto says
that I should be OK having kdebase using split ebuilds and others KDE
parts using th old monolithic way. Is this working for anyone? Anyone
else run into similar problems or have ideas about what the heck is
going wrong? I tried removing all my old ~/.kde dirs but that didn't
fix it. Appreciate any pointers.
-Wes
--
gentoo-user@gentoo.org mailing list
reply other threads:[~2005-09-23 23:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050923225607.GA18249@beavis \
--to=smiths@alumni.cse.ucsc.edu \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox