public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question
Date: Wed, 26 Aug 2009 12:08:43 +0200 (CEST)	[thread overview]
Message-ID: <tkrat.6a547c1995585d9f@igpm.rwth-aachen.de> (raw)
In-Reply-To: <4A950659.8020704@gmail.com>

On 26 Aug, Dale wrote:
> Helmut Jarausch wrote:
>> On 26 Aug, Dale wrote:
>>   
>>> Helmut Jarausch wrote:
>>>     
>>>> On 16 Aug, Dirk Heinrichs wrote:
>>>>   
>>>>       
>>>>> Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs:
>>>>>
>>>>>     
>>>>>         
>>>>>> 2) No need to unmerge anything (except one or two blockers).
>>>>>>       
>>>>>>           
>>>>> However, you can unmerge 4.2.x, if you like to.
>>>>>
>>>>>     
>>>>>         
>>>> How to do that in a simple way?
>>>>
>>>> Unfortunately, 
>>>> emerge --unmerge kde-base/kde-meta:4.2
>>>> only unmerges the meta package itself.
>>>>
>>>> Thanks for a hint ( I'm afraid of any kde updates
>>>> since they always have created more headaches than any
>>>> other package or set of packages )
>>>>
>>>>   
>>>>       
>>> Not tested but should work.  Use the -p option to make sure.
>>>
>>> Unmerge kde-meta:4.2
>>> emerge --depclean -p
>>>
>>> If that looks good, remove the -p.  It should only remove kde:4.2 and
>>> what depends on it.  If you wait a while, I may be about to do this. 
>>> I'm doing the same thing as you.  This DSL is soooooo cool.  :-) 
>>>
>>>     
>>
>> I have difficulties doing so. 'emerge --depclean' requires a recent
>> emerge --update --newuse --deep @system @world
>> which tries to update kde, as well.
>> I'm just trying to mask all kde-base packages, then doing emerge
>> --update --newuse --deep @system @world
>>
>> Still, quite tedious.
>> Helmut.
>>
>>   
> 
> It may not work but then again it might.  emerge --depclean -p
> kde-meta:4.2 .

This gives

>>> No packages selected for removal by depclean

Helmut.




  reply	other threads:[~2009-08-26 20:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-16 19:02 [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question Roy Wright
2009-08-16 19:12 ` Dirk Heinrichs
2009-08-16 19:26   ` Dirk Heinrichs
2009-08-26  7:25     ` Helmut Jarausch
2009-08-26  7:40       ` Alan McKinnon
2009-08-26  7:48       ` Dale
2009-08-26  9:23         ` Helmut Jarausch
2009-08-26  9:54           ` Dale
2009-08-26 10:08             ` Helmut Jarausch [this message]
2009-08-26 10:10           ` Alan McKinnon
2009-08-26 16:31       ` Dirk Heinrichs
2009-08-16 19:29   ` Alan McKinnon
2009-08-16 19:46     ` Volker Armin Hemmann
2009-08-16 20:48       ` Alan McKinnon
2009-08-16 21:09         ` Volker Armin Hemmann
2009-08-16 21:18           ` Alan McKinnon
2009-08-16 21:33             ` Volker Armin Hemmann
2009-08-16 22:12               ` Roy Wright
2009-08-17  5:37                 ` Dirk Heinrichs
2009-08-17 22:40                 ` [gentoo-user] [solved] " Roy Wright
2009-08-17  5:44             ` [gentoo-user] " Dirk Heinrichs
2009-08-19 18:39 ` Alex Schuster
2009-08-19 21:56   ` John H. Moe
2009-08-19 22:44     ` Alex Schuster

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=tkrat.6a547c1995585d9f@igpm.rwth-aachen.de \
    --to=jarausch@igpm.rwth-aachen.de \
    --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