[This is the third time sending this post because it doesn't seem to be
showing up on the list. Sorry if it ends up being a duplicate (or a
triplicate).]
Thank you everyone!
I have now discovered that my problem was that I still had some monolithic kde
packages hanging around alongside the
Thank you everyone!
I have now discovered that my problem was that I still had some monolithic kde
packages hanging around alongside the metapackages (e.g. kdeedu instead of
kdeedu-meta). I think I'd been unmerging them one at a time and didn't get
around to finishing the job. Now that I
On Saturday 22 October 2005 04:07 pm, Robert Persson wrote:
I know I can emerge kdebase-meta kdeaddons-meta kdeblahblahblah to get
things up to date, but is there a way to get portage to actually deal with
kde nicely like it used to?
Just emerge kde, you don't need to work with the meta
* Robert Persson ([EMAIL PROTECTED]) wrote:
I emerged kde 3.4 using the metapackages (kdebase-meta, kdeaddons-meta etc.).
However I now find that emerge -u world fails to update any of the component
try: emerge -uD world
--
gentoo-user@gentoo.org mailing list
Robert Persson wrote:
I emerged kde 3.4 using the metapackages (kdebase-meta, kdeaddons-meta etc.).
However I now find that emerge -u world fails to update any of the component
packages to their latest versions, which should all be 3.4.1(-r2/r3/etc). I
end up emerging newer versions
5 matches
Mail list logo