public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Haney" <mhaney@ercbroadband.org>
To: <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64]  Re: Following the kde4.1 upgrade guide
Date: Wed, 29 Oct 2008 08:18:56 -0400	[thread overview]
Message-ID: <490854B0.7080802@ercbroadband.org> (raw)
In-Reply-To: <pan.2008.10.28.23.15.39@cox.net>

Duncan wrote:

> 
> Yes.

Here's my problem, when I follow the documentation, I put the file in 
package.keywords, and that doesn't unmask them when I do an emerge 
--update.  At this point, I think the documentation is wrong and that 
should be placed in package.unmask, right?

> 
> FWIW, I run FEATURES=buildpkg so I always have binpkgs for what's 
> installed, but otherwise I'd consider quickpkging the existing KDE before 
> you upgrade, just in case something doesn't work on the upgrade.  Then 
> I'd unmerge the existing kde4, so it didn't screw anything up going to 
> the new version.

You know, I've never used that feature before, or in fact built any 
packages as backups.  Got any tips or link to show me the best way to 
handle it?

> 
> BTW, if you are still running kde3 as well, I strongly recommend 
> USE=kdeprefix.  Unfortunately there's a ways to go in getting the 
> unprefixed kde4 to stay out of the way of kde3.  People are having 
> problems with kde3 apps because the config search path is the normal dirs 
> (/usr/share/config and friends) before the prefix dirs 
> (/usr/kde/3.5/share/config and friends), and if kde4 is installed without 
> kdeprefix, it installs to the normal dirs, screwing up the config for 
> kde3 packages.  This system config problem is quite apart from the user 
> config issues, which are more or less solved at this point, provided you 
> follow instructions (or were using separate user accounts for kde3 and 
> kde4, as recommended way earlier).
> 

Actually, I do have 3.5.9 on this box and I've yet to go back to it now 
that 4.1.1 is on it.  However, I'd already decided to use kdeprefix 
anyway, mainly because I feel more comfortable moving through that 
upgrade path than NOT using it.



-- 
Libenter homines id quod volunt credunt -- Caius Julius Caesar


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support



      reply	other threads:[~2008-10-29 12:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 17:54 [gentoo-amd64] Following the kde4.1 upgrade guide Mark Haney
2008-10-28  5:42 ` [gentoo-amd64] " Duncan
2008-10-28 14:20   ` Mark Haney
2008-10-28 23:15     ` Duncan
2008-10-29 12:18       ` Mark Haney [this message]

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=490854B0.7080802@ercbroadband.org \
    --to=mhaney@ercbroadband.org \
    --cc=gentoo-amd64@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