From: "Michael Kintzios" <michaelkintzios@lycos.co.uk>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] KDE 3.5
Date: Thu, 1 Dec 2005 13:41:10 -0000 [thread overview]
Message-ID: <F49BE7328A1DA246AFC5C2CDDB86D917DFB127@BCV0X134EXC0005> (raw)
In-Reply-To: <438EF698.4030105@gmail.com>
> -----Original Message-----
> From: Mrugesh Karnik [mailto:mrugeshkarnik@gmail.com]
> Sent: 01 December 2005 13:12
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] KDE 3.5
>
>
> Thiago Lüttig wrote:
> > how do you installed it ? i mean, the emerge parameters ?? :D
>
> I just did emerge --udpate --deep world. It slotted 3.4 and 3.5, so I
> first cleared out my distfiles to free up some space! Then, edited
> /etc/rc.conf to set XSESSION="kde-3.5". After restarting
> /etc/init.d/xdm, kdm-3.5 came up with entries for both 3.4
> and 3.5. Some
> packages are still being compiled. I'll keep 3.4 till all of them are
> compiled and then unmerge 3.4.
If you have an old monolithic KDE install (in my case KDE-3.2.x) and
would like to unmerge it along with all the kde 3.2.x packages and
exclusive dependencies to save some space, how would you do it? How
could one ensure that there will be no apps/deps out there, which will
try to re-emerge this old version afresh?
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-01 13:57 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 11:12 [gentoo-user] KDE 3.5 Thiago Lüttig
2005-12-01 11:45 ` Dale
2005-12-01 12:06 ` Neil Bothwick
2005-12-01 11:50 ` Mrugesh Karnik
2005-12-01 11:58 ` Thiago Lüttig
2005-12-01 13:11 ` Mrugesh Karnik
2005-12-01 13:29 ` Neil Bothwick
2005-12-01 17:01 ` Mrugesh Karnik
2005-12-01 17:14 ` Kumar Golap
2005-12-01 17:44 ` Mrugesh Karnik
2005-12-02 0:31 ` Dale
2005-12-02 6:46 ` Robert Crawford
2005-12-02 7:39 ` Dale
2005-12-02 9:03 ` Neil Bothwick
2005-12-02 9:17 ` Dale
2005-12-02 9:39 ` Dirk Heinrichs
2005-12-02 10:13 ` Dale
2005-12-02 9:49 ` Neil Bothwick
2005-12-02 10:14 ` Dale
2005-12-01 18:13 ` Petteri Räty
2005-12-01 13:41 ` Michael Kintzios [this message]
2005-12-01 17:21 ` Kevin Hanson
2005-12-01 11:58 ` Uwe Klosa
2005-12-01 12:24 ` Dale
2005-12-01 12:53 ` Uwe Klosa
2005-12-01 13:31 ` Neil Bothwick
2005-12-01 14:13 ` Dale
2005-12-01 12:17 ` fire-eyes
2005-12-01 12:35 ` Hemmann, Volker Armin
2005-12-01 15:02 ` Martins Steinbergs
2005-12-02 8:01 ` Christian Panten
2005-12-02 8:25 ` Dale
2005-12-02 13:03 ` Nagatoro
2005-12-02 13:12 ` Dale
2005-12-02 13:35 ` Boyd Stephen Smith Jr.
2005-12-02 13:51 ` Neil Bothwick
2005-12-02 14:11 ` Dale
2005-12-02 15:19 ` Neil Bothwick
2005-12-03 0:25 ` Robert Crawford
2005-12-02 13:32 ` Uwe Klosa
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 19:05 Rafael Fernández López
2006-05-27 4:04 Anthony E. Caudel
2006-05-27 4:40 ` Manuel McLure
2006-05-27 5:36 ` Hemmann, Volker Armin
2006-05-27 6:03 ` Anthony E. Caudel
2006-05-27 14:41 ` Hemmann, Volker Armin
2006-05-27 15:01 ` fire-eyes
2006-05-27 17:37 ` Hemmann, Volker Armin
2006-05-29 20:52 ` Daniel
2006-05-29 21:35 ` Hemmann, Volker Armin
2006-05-27 6:15 ` Steven Susbauer
2006-05-27 6:06 ` Richard Fish
2006-05-27 6:41 ` Anthony E. Caudel
2006-05-27 7:56 ` Neil Bothwick
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=F49BE7328A1DA246AFC5C2CDDB86D917DFB127@BCV0X134EXC0005 \
--to=michaelkintzios@lycos.co.uk \
--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