On Thursday 26 November 2009 19:20:26 Alan McKinnon wrote:
On Thursday 26 November 2009 19:34:34 James wrote:
kde-4.3.1 went smooth, except
for I have to manually removed all the kde-3.5 packages.
It had kde-meta-3.5.10. Is there some syntax or a better
method to insure all the kde-3.5.x
/kate
kde-base/kcalc
kde-base/kcharselect
kde-base/kcheckpass
kde-base/kcminit
kde-base/kcontrol
kde-base/kcron
kde-base/kdeadmin-meta--Yes
kde-base/kdeartwork-emoticons
kde-base/kdeartwork-iconthemes
kde-base/kdeartwork-kscreensaver
kde-base/kdeartwork-meta--Yes
kde-base/kdeartwork-sounds
kde-base
On Tuesday 08 April 2008, Michael Schmarck wrote:
Alan McKinnon [EMAIL PROTECTED] wrote:
The other option is to use the kde*meta ebuilds, which do directly
depend on the sub-ordinate packages. This is what I do and I don't
get the effect you observed.
Thanks.
I think I removed kde-meta
$ ls /usr/portage/kde-base/ | grep meta
kdeaccessibility-meta
kdeaddons-meta
kdeadmin-meta
kdeartwork-meta
kdebase-meta
kdebindings-meta
kdeedu-meta
kdegames-meta
kdegraphics-meta
kde-meta
kdemultimedia-meta
kdenetwork-meta
kdepim-meta
kdesdk-meta
kdetoys-meta
kdeutils-meta
kdewebdev-meta
5.7.4.
>
> Thanks for your support.
I'm not sure how long that will take.
I've been running 5.7.4 without any obvious issues for a while now...
Attached is the "package.accept_keywords" file I use for 5.7.4
It's up to you to decide, but every time you log-out, you'll have the same
On Thursday 23 June 2011 13:09:53 Neil Bothwick did opine thusly:
On Thu, 23 Jun 2011 05:49:45 -0500, Dale wrote:
My question was why are you installing cantor if you don't
need it?
Oh, I see. It was pulled in by kde-meta. I know I can have KDE
other ways but it is much easier
On 24/06/2019 14:00, Mick wrote:
I've installed plasma-meta plus some kde-apps meta packages as follows:
kde-apps/kdeadmin-meta
kde-apps/kdecore-meta
kde-apps/kdegraphics-meta
kde-apps/kdemultimedia-meta
kde-apps/kdenetwork-meta
kde-apps/kdepim-meta
kde-apps/kdeutils-meta
kde-apps
/kdepim-meta:4.1
# KDE deps
=kde-base/qimageblitz-0.0*
# KDE base libs
kde-base/kdelibs:4.1
kde-base/kdepimlibs:4.1
kde-base/libkcddb:4.1
kde-base/libkcompactdisc:4.1
kde-base/libkdcraw:4.1
kde-base/libkdeedu:4.1
kde-base/libkdepim:4.1
kde-base/libkexiv2:4.1
kde-base/libkholidays:4.1
kde-base
~kde-base/kcharselect-4.2.0
~kde-base/kcheckpass-4.2.0
~kde-base/kcminit-4.2.0
~kde-base/kcmshell-4.2.0
~kde-base/kcolorchooser-4.2.0
~kde-base/kcontrol-4.2.0
~kde-base/kcron-4.2.0
~kde-base/kdeaccessibility-colorschemes-4.2.0
~kde-base/kdeaccessibility-iconthemes-4.2.0
~kde-base/kdeaccessibility-meta
On Mittwoch 11 Februar 2009, James wrote:
Hello,
OK, I have read back into January the suggestions on this
list about going to Kde-meta 4.2. I have dozens of workstations
running gentoo, so now I'm going to upgrade one (test) laptop
to get a feel for kde-4.2 and hopefully flesh out
/kcontrol ~x86
kde-base/kcron ~x86
kde-base/kdat ~x86
kde-base/kdcop ~x86
kde-base/kde ~x86
kde-base/kde-env ~x86
kde-base/kde-i18n ~x86
kde-base/kde-meta ~x86
kde-base/kdeaccessibility ~x86
kde-base/kdeaccessibility-iconthemes ~x86
kde-base/kdeaccessibility-meta ~x86
kde-base/kdeaddons ~x86
kde-base
in order to make portage
happy about conflicts:
[/etc/portage/package.use]
kde-base/kdebase-startkde -wallpapers
kde-apps/kdebase-meta -wallpapers
(Yes, it took forever to do that manually.)
I suspect it will probably not work now but it'll be a starting point if
you want to try this method. May
Volker Armin Hemmann volkerarmin at googlemail.com writes:
6. emerge -DNv kde-meta
Look plausible? Verbose comments are most welcome.
just emerge the kde-4.2 set instead of that meta stuff.
Is there a problem with kde-meta-4.2.0 ? I have many different
users asking for many different
Hi,
I am trying to upgrade to kde 3.5.2
specifically because my current KDE was installed with emerge kde-meta
I have added the appropriate dependencies to
/etc/portage/package.keywords
kde-base/arts
~x86
kde-base/kdelibs ~x86
kde-base
On Thursday 26 November 2009 22:59:24 Mick wrote:
On Thursday 26 November 2009 19:20:26 Alan McKinnon wrote:
On Thursday 26 November 2009 19:34:34 James wrote:
kde-4.3.1 went smooth, except
for I have to manually removed all the kde-3.5 packages.
It had kde-meta-3.5.10. Is there some
Paul Hartman wrote:
On Wed, Sep 9, 2009 at 3:41 AM, Dale rdalek1...@gmail.com wrote:
--depclean wanted to remove KDE 3. :-(
You don't have it in world?
I had kde-meta in there but not the specific version. I now have it in
the world file this way:
r...@smoker / # cat /var
Wes Gray wrote:
# emerge -p kde-meta
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] kde-base/kde-meta-3.4.1
I tried emerging kde-meta. I then tried unmerging all the blockers it
created and then emerging back kde, to get rid of kde
On Thu, 22 Jun 2006 16:28:42 + (UTC), James wrote:
Is there an easy way to remove all of the kde packages before
migration to kde-meta?
See the thread form a couple of hours ago, but one easy way is
emerge -Ca $(ls /var/db/pkg/kde-base)
I like having as many kde apps installed
Hello,
OK, I have read back into January the suggestions on this
list about going to Kde-meta 4.2. I have dozens of workstations
running gentoo, so now I'm going to upgrade one (test) laptop
to get a feel for kde-4.2 and hopefully flesh out an
upgrade strategy for all of these laptops
get this:
r...@smoker / # equery list -p kde-meta
[ Searching for package 'kde-meta' in all categories among: ]
* installed packages
[I--] [ ] kde-base/kde-meta-3.5.10 (3.5)
[I--] [ ~] kde-base/kde-meta-4.3.5 (4.3)
* Portage tree (/usr/portage)
[-P-] [ ] kde-base/kde-meta-4.3.3 (4.3)
[-P
On Mon, 23 Feb 2009 04:03:10 -0600, Dale wrote:
Lets say I have a set named dk-kde, with the prefix Allen suggested, and
I put kde-meta in that file. Would that emerge all the KDE or just that
one package? I emerged kde-meta to install KDE so that is all there is
in my world file right now
On Sat, 10 Dec 2005 10:31:26 -0600, Harry Putnam wrote:
I'm confused here. (even more..)
Before starting the compile:
I ran a comparision of `emerge -v -p kde' and
emerge -v -p kde-meta
The last showed a much larger pile of dependancies than the former.
A longer list, but not larger
this:
ebuild NS ] kde-base/kdebase-meta-4.4.5 [4.5.1] USE=(-aqua) (-kdeprefix)
0 kB
[uninstall] kde-base/kdebase-meta-4.5.1 USE=(-aqua) (-kdeprefix)
[blocks b ] kde-base/kdebase-meta:4.5[-kdeprefix] (kde-base
of output for KDE-components like this:
ebuild NS ] kde-base/kdebase-meta-4.4.5 [4.5.1] USE=(-aqua)
(-kdeprefix) 0 kB
[uninstall] kde-base/kdebase-meta-4.5.1 USE=(-aqua) (-kdeprefix)
[blocks b ] kde-base/kdebase-meta:4.5[-kdeprefix] (kde-base/kdebase-
meta:4.5[-kdeprefix] is blocking kde
changed-use world
--pretend gives a lot of output for KDE-components like this:
ebuild NS ] kde-base/kdebase-meta-4.4.5 [4.5.1] USE=(-aqua)
(-kdeprefix) 0 kB
[uninstall] kde-base/kdebase-meta-4.5.1 USE=(-aqua) (-kdeprefix)
[blocks b ] kde-base/kdebase-meta:4.5[-kdeprefix] (kde-base
On Tue, 2005-12-06 at 18:19 -0600, Boyd Stephen Smith Jr. wrote:
I've just completed an upgrade to kde-meta-3.5 from kde-meta-3.4 -- what's
the beast way to clean up all the old kde 3.4 packages.
emerge -C kde-meta; emerge --depclean
doesn't work: depclean does not show any of the kde 3.4
Ian K schreef:
I didn't know about this kde-meta package..
Will it get me 3.4.1?
Ian
http://packages.gentoo.org/search/?sstring=kde-meta
kde-meta
Description: kde - merge this to pull in all kde packages
Releasesalpha amd64 arm hppaia64mipsppc ppc64
ppc
On Friday 15 June 2007, Alexander Skwar [EMAIL PROTECTED] wrote
about '[gentoo-user] Make portage assume, that a package is installed':
Good morning!
On my system, I did not install net-dialup/ppp.
But I'd now like to install kde-base/kde-meta, which will
pull in kde-base/kdenetwork-meta
On Sat, 30 May 2020 22:46:18 +0100, Peter Humphrey wrote:
> > The point of meta packages is that they install a whole set of stuff,
> > in this case "Merge this to pull in all Plasma 5 packages". If you
> > don't want the kitchen sink, don't use meta packages.
Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
However, I suggest that a cleaner method would be to not install kde-meta
or kdenetwork-meta at all but instead just install the KDE applications
that you require.
Actually, I disagree.
This would (obviously *g*) mean, that kde-meta cannot
-base/kde * ~x86
kde-base/kde-env * ~x86
kde-base/kde-i18n ~x86
kde-base/kde-meta ~x86
kde-base/kdeaccessibility * ~x86
kde-base/kdeaccessibility-iconthemes ~x86
kde-base/kdeaccessibility-meta ~x86
kde-base/kdeaddons * ~x86
kde-base/kdeaddons-docs-konq-plugins ~x86
kde-base/kdeaddons-kfile-plugins
On Monday, 24 June 2019 21:16:51 BST Dale wrote:
> I went through this a few years ago. I had some large programs
> installed that I didn't use, Kmail and others. I wanted to clean them
> out but at the time I had installed KDE with kde-meta. Basically, that
> installs everything
in kde-base. It's equivalent to Neils suggestion.
# cd /var/db/pkg emerge -Cva kde-base/*
I then removed the monolithci packages by hand that are blocking
This is the command I used to see what is(was) blocking kde-meta:
emerge -uavDN kde-meta
Also after removing old slots there may still
to check that you
have installed:
kde-base/kdemultimedia-meta
kde-base/kdemultimedia-kioslaves
If you're using a good chunk of kde, emerge kde-base/kde-meta. Makes
kde upgrades simpler, and less pollution in the world file.
To be honest, I don't want meta anything, bur from what I understand
I installed KDE yesterday via emerge kde -vuD, and just remembered
today about kde-meta, which installs a lot more. In running emerge
kde-meta -vuD, I get 250 new packages, and 245 blocks, with 1 upgrade.
What is the _best_ path forward? Should I just stick with my current
build of kde
· Boyd Stephen Smith Jr. [EMAIL PROTECTED]:
On Friday 15 June 2007, Alexander Skwar [EMAIL PROTECTED] wrote
about '[gentoo-user] Re: Finer grained kde*-meta packages':
Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
On Friday 15 June 2007, Alexander Skwar [EMAIL PROTECTED]
But maybe
On Friday 15 June 2007, Alexander Skwar [EMAIL PROTECTED] wrote
about '[gentoo-user] Finer grained kde*-meta packages (was: Make portage
assume, that a package is installed)':
Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
However, I suggest that a cleaner method would be to not install
On Sun, 01 Feb 2009 12:41:35 -0600, Dale wrote:
emerge -C kde
emerge --depclean -a
emerge -av kde-meta
That's what I was afraid of. Sigh. Thanks.
Could he just emerge -C kde then re-emerge whatever he wanted without
having to reinstall all of KDE? Isn't
On Thursday 01 March 2007 18:06:47 Turi Tropea wrote:
hi everyone,
after a fresh installation of gentoo (using the minimal cd)
i try to emerge kde-meta kde-i18n kdm
but an error was occured, 41 package blocks the emerge
there is the output of the emerge --pretend and package.keyword .use
Did you check out the Gentoo docs on kde split ebuilds? It has a lot of good
info. I started to emerge with the kde and then decided to go with the meta
so per the instructions I had to remove some stuff - it shows up as blocked.
On Saturday 10 December 2005 11:31, Harry Putnam wrote:
Neil
On Wed, Oct 19, 2011 at 03:51, Mick michaelkintz...@gmail.com wrote:
To listen to audio CDs you should *not* mount the CD. Therefore the above
entry is not required.
Since you are trying to use KDE apps to play CDs you ought to check that you
have installed:
kde-base/kdemultimedia-meta
On 10/5/05, Wes Gray [EMAIL PROTECTED] wrote:
# emerge -p kde-metaThese are the packages that I would merge, in order:Calculating dependencies ...done![ebuild R ] kde-base/kde-meta-3.4.1I tried emerging kde-meta.I then tried unmerging all the blockers it
created and then emerging back kde, to get
On Mittwoch 11 Februar 2009, james wrote:
Volker Armin Hemmann volkerarmin at googlemail.com writes:
6. emerge -DNv kde-meta
Look plausible? Verbose comments are most welcome.
just emerge the kde-4.2 set instead of that meta stuff.
Is there a problem with kde-meta-4.2.0 ? I have
On Jan 24, 2008 8:42 PM, maxim wexler [EMAIL PROTECTED] wrote:
snip
#eix-sync. Then #emerge autounmask and ran
#autounmask kde-base/kde-meta-4.0.0
which completed w/o error.
$eix kde picks up the new version:
...
* kde-base/kde
Available versions: 3.5.5:3.5 3.5.6:3.5
3.5.7:3.5
James wrote:
Thanks for the suggestion. I get the feeling we're all hacking our own
install semantics here for kde-4.2.
I find the -meta packages very helpful. Instead of pulling in all of
KDE (with tons of stuff I don't need), I simply emerged those:
kde-base/ark
kde-base/kate
kde
to meta..
Did you look at [1] too?
Is there an easy way to remove all of the kde packages before
migration to kde-meta?
Sure. But it would remove packages that the meta packages depend on too.
kde-base/kdelibs takes a long time to compile and hence shouldn't be removed
as you still need
BRM wrote:
I installed KDE yesterday via emerge kde -vuD, and just remembered
today about kde-meta, which installs a lot more. In running emerge
kde-meta -vuD, I get 250 new packages, and 245 blocks, with 1 upgrade.
What is the _best_ path forward? Should I just stick with my current
build
them
> > out but at the time I had installed KDE with kde-meta.
Basically, that
> > installs everything KDE, wanted or not. I uninstalled that and
went
>
> > these instead:
> According to the current wiki page these days the kde-meta has been
replaced
> with plasma-meta.
Neil Bothwick neil at digimed.co.uk writes:
emerge xorg-x11
That's a meta-package, you only need to install xorg-server. This
is not pulled in by KDE because a local X server is not a requirement to
run KDE, although KDE does depend on several X11 libraries.
Hmm, nice to know.
Where do
On Sat, 2009-04-11 at 12:58 +0100, Neil Bothwick wrote:
On Sat, 11 Apr 2009 19:44:01 +0800, William Kenworthy wrote:
Its just dawned on me that this is kde-meta - is there a way to just
remove all kde at once?
emerge -C kde-meta
emerge --depclean -a
Thanks Neil, I used the xarg way
On Sun, 26 Jun 2005 23:07:59 +0200, q-parser wrote:
I've just emerged kde-meta-3.4.1, but it won't start after issuing
startx. I changed XSESSION in /etc/rc.conf to kde-meta-3.4.1 but
still nothing.
I think it should be kde-3.4.1, no meta, but I've always used a plain
kde and it picks up
* On Jun 2 20:21, Mick (gentoo-user@lists.gentoo.org) wrote:
What's the best way to find out what -meta packages exist
eix 'kde.*-meta'
and what they contain?
The KDE website is pretty good for that - see here:
http://kde.org/whatiskde/project.php#distribution
Tom
--
gentoo-user@gentoo.org
may be useful to
other users:
emerge PyQt with USE=webkit sql
I had installed a few kde-meta packages rather than the full kde-meta.
eix -I kde | grep meta list your installed kde-meta packages
Add the kde4 versions of those meta packages to package.mask:
(Sample) package.mask to mask kde4
-r1)
[blocks B ] =kde-base/kimagemapeditor-3.4* (is blocking
kde-base/kdewebdev-3.4.3-r1)
[blocks B ] =kde-base/quanta-3.4* (is blocking kde-base/kdewebdev-3.4.3-r1)
It looks like you installed KDE originally using the split ebuilds -
i.e. kde-meta instead of kde. Try
emerge --pretend
On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote:
[EMAIL PROTECTED]:/# emerge --pretend kde-meta
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[blocks B ] =kde-base/kdebase-3.4* (is blocking
kde-base/kscreensaver-3.4.1)
You currently
Neil Bothwick neil at digimed.co.uk writes:
Is there an easy way to remove all of the kde packages before
migration to kde-meta?
See the thread form a couple of hours ago,
Awe, yes, Gmane runs very slow during the day (EST),
I see this recent discussion.
I think you have
On Sat, 11 Apr 2009 19:44:01 +0800, William Kenworthy wrote:
Its just dawned on me that this is kde-meta - is there a way to just
remove all kde at once?
emerge -C kde-meta
emerge --depclean -a
--
Neil Bothwick
I couldn't repair your brakes, so I made your horn louder.
signature.asc
-meta-4.3.1 (=kde-base/kate-4.3.1:4.3[kdeprefix=])
kde-base/kdesdk-meta-4.3.3 (!kdeprefix ?
=kde-base/kate-4.3.3[-kdeprefix]) (kdeprefix ?
=kde-base/kate-4.3.3:4.3[kdeprefix])
OK, but I am getting this much - slightly different to yours above:
# equery depends -a kate
Neil Bothwick neil at digimed.co.uk writes:
Sets are a replacement for meta-packages, so your set would contain the
packages you need. If it did contain kde-meta, then it would install all
of KDE, because that is a dependency of kde-meta.
OK, color me dense, but, if we are assuming
On Mittwoch, 2. Januar 2008, BRM wrote:
I installed KDE yesterday via emerge kde -vuD, and just remembered
today about kde-meta, which installs a lot more. In running emerge
kde-meta -vuD, I get 250 new packages, and 245 blocks, with 1 upgrade.
What is the _best_ path forward? Should I just
On Tuesday 24 February 2009 05:33:40 James wrote:
Neil Bothwick neil at digimed.co.uk writes:
Sets are a replacement for meta-packages, so your set would contain the
packages you need. If it did contain kde-meta, then it would install all
of KDE, because that is a dependency of kde-meta
Alan McKinnon wrote:
On Tuesday 24 February 2009 05:33:40 James wrote:
Neil Bothwick neil at digimed.co.uk writes:
Sets are a replacement for meta-packages, so your set would contain the
packages you need. If it did contain kde-meta, then it would install all
of KDE, because
.
You must have something badly wrong with your @system. kde-meta depends on:
RDEPEND=
$(add_kdebase_dep kate)
$(add_kdebase_dep kdeadmin-meta)
$(add_kdebase_dep kdeartwork-meta)
$(add_kdebase_dep kdebase-meta)
$(add_kdebase_dep kdeedu-meta
to avoid that - there is a strict one-to-one mapping
between what the -meta packages install and what is shipped in the
upstream tarballs by KDE
Sorry I'm being rather dense with this ... are you saying that the DEPENDs
listed when you run 'equery depends -a kate' are different to mine because
in more than one -meta package and
the devs seem to want to avoid that - there is a strict one-to-one
mapping between what the -meta packages install and what is shipped in
the upstream tarballs by KDE
Sorry I'm being rather dense with this ... are you saying that the
DEPENDs listed
Neil Bothwick wrote:
On Mon, 23 Feb 2009 04:03:10 -0600, Dale wrote:
Lets say I have a set named dk-kde, with the prefix Allen suggested, and
I put kde-meta in that file. Would that emerge all the KDE or just that
one package? I emerged kde-meta to install KDE so that is all
Willie Wong wrote:
On Tue, Dec 01, 2009 at 08:24:02AM -0600, Penguin Lover Dale squawked:
emerge: there are no ebuilds to satisfy ~net-libs/ortp-0.7.1.
(dependency required by kde-base/kopete-3.5.10-r4 [ebuild])
(dependency required by kde-base/kdenetwork-meta-3.5.10 [installed])
(dependency
Neil Bothwick [EMAIL PROTECTED] writes:
kde-base/kde is a meta package, it pulls in all the monolithic KDE
builds. If you are concerned about installation compile times, you should
not be trying to build the whole of KDE. Do you really need all of
kdegames, kdeedu and kdetoys to get your
/kde-meta-3.4.1 (3.4)
# ls /usr/kde
3 3.1 3.2 3.3 3.4
#
Is there a utility which shows all the installed packages?
--
gentoo-user@gentoo.org mailing list
On Saturday 28 November 2009 02:01:22 Mick wrote:
To find out what depends on kate, kweather and kfloppy, use the correct
portage tool:
a...@nazgul ~ $ equery depends -a kate
* Searching for kate ...
kde-base/kdesdk-meta-4.3.1 (=kde-base/kate-4.3.1:4.3[kdeprefix=])
kde-base/kdesdk
Jamie Dobbs wrote:
The unfortunate thing about that it it doesn't appear to accept the
'meta-package' to cover everything and I'm still trying to work out
all the packages that need to be added.
Ugh...
# grep --no-filename deprange
/usr/portage/kde-base/*-meta/*-meta-3.4.0.ebuild | sort
Bo Ørsted Andresen bo.andresen at zlin.dk writes:
The revdep-rebuild is good *after* emerging kde-meta. It will recompile third
party applications such as amarok against the new version of kde-meta. I
posted the simple steps at the bottom of my previous mail.
Assuming you really
do want
Alan McKinnon alan.mckinnon at gmail.com writes:
grep kde /var/lib/portage/world
only kde-meta in there
emerge -a --depclean
yep, just making sure as I thought there might be a
very special syntax to remove all kde 3.5.*
I used revdep-rebuild and emerge -uDNvp world to get the
list
Alan McKinnon wrote:
On Thursday 26 November 2009 19:34:34 James wrote:
kde-4.3.1 went smooth, except
for I have to manually removed all the kde-3.5 packages.
It had kde-meta-3.5.10. Is there some syntax or a better
method to insure all the kde-3.5.x packages are removed,
without a manual
Peter Humphrey wrote:
On Wednesday 22 June 2011 16:50:10 Dale wrote:
If you use KDE like me, be prepared to put the thing back tho. Some KDE
packages depend on things that seem to need it enabled.
Looks like it's only packages that are pulled in by kdeedu-meta. Do you need
all
On Thu, Jun 23, 2011 at 3:36 PM, Dale rdalek1...@gmail.com wrote:
SNIP
I install with kde-meta. It pulls about all things KDE in with that. For
me, it is better to use kde-meta than to do it any other way. Even with
kde-meta, I think there is a few that I still had to emerge manually.
kde
packages.
Install kdebase-meta, kdenetwork-meta, kdepim-meta etc. kde-meta is for
those that want to install everything.
Thanks for all the replies. What's the best way to find out what
-meta packages exist and what they contain?
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list
?
Hello Mick,
I'm just not certain any more exactly which packages belong to
which meta(kde) package. I think they are added and dropped
over the last few years, resulting in a dynamic grouping
or like those you mentioned, not being picked up by and of the
kde-meta packages.
You
On Friday 15 June 2007, Alexander Skwar [EMAIL PROTECTED] wrote
about '[gentoo-user] Re: Finer grained kde*-meta packages':
Suppose you've got the following use case: Install all of
KDE, but leave out PPP stuff.
How would you solve that?
Intall all the kde*-meta packages except kde-meta (I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James wrote:
kde-meta is ideal for me. I thought it was going away?
Since kde(4)-meta is alive and well, that is my preferred
method. I hope when kde-meta goes away (?) there is a migration
plan? When this whole kde4 venture started for me (feb 09
David Corbin wrote:
On Sunday 31 July 2005 05:59 pm, Neil Bothwick wrote:
On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote:
[EMAIL PROTECTED]:/# emerge --pretend kde-meta
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[blocks B ] =kde
:4.3
kde-base/kdeartwork-desktopthemes:4.3
kde-base/kdeartwork-emoticons:4.3
kde-base/kdeartwork-iconthemes:4.3
kde-base/kdeartwork-kscreensaver:4.3
kde-base/kdeartwork-meta:4.3
kde-base/kdeartwork-sounds:4.3
kde-base/kdeartwork-styles:4.3
kde-base/kdeartwork-wallpapers:4.3
kde-base/kdeartwork
-base/kcontrol:4.3
kde-base/kde-env:4.3
kde-base/kdeartwork-colorschemes:4.3
kde-base/kdeartwork-desktopthemes:4.3
kde-base/kdeartwork-emoticons:4.3
kde-base/kdeartwork-iconthemes:4.3
kde-base/kdeartwork-kscreensaver:4.3
kde-base/kdeartwork-meta:4.3
kde-base/kdeartwork-sounds:4.3
kde-base/kdeartwork
/kcmshell:4.3
kde-base/kcolorchooser:4.3
kde-base/kcontrol:4.3
kde-base/kde-env:4.3
kde-base/kdeartwork-colorschemes:4.3
kde-base/kdeartwork-desktopthemes:4.3
kde-base/kdeartwork-emoticons:4.3
kde-base/kdeartwork-iconthemes:4.3
kde-base/kdeartwork-kscreensaver:4.3
kde-base/kdeartwork-meta:4.3
kde-base
Daniel D Jones wrote:
Currently running KDE 3.3. I get the following:
[EMAIL PROTECTED]:/# emerge --pretend kde-meta
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[blocks B ] =kde-base/kdebase-3.4* (is blocking
kde-base/kscreensaver-3.4.1
to me that this was the same problem, since that block
referenced a 3.5.10 package and mine referenced a 3.5.9 package.
However, upgrading to 3.5.10 raises another issue. For 3.5, I didn't install
the meta package, I installed the KDE base package:
ROOT / # eix -e kde
[I] kde-base/kde
-expat-upgrading.xml
Maybe I should explain a bit more in detail how the OP should fix this,
as finding kde blockers between the -meta and monolithic ebuilds is not
a cut and dried process.
First, I assume he has read the emerging KDE howto on the gentoo docs
site, and understands the difference
/kdeartwork-iconthemes:4.3
kde-base/kdeartwork-kscreensaver:4.3
kde-base/kdeartwork-meta:4.3
kde-base/kdeartwork-sounds:4.3
kde-base/kdeartwork-styles:4.3
kde-base/kdeartwork-wallpapers:4.3
kde-base/kdeartwork-weatherwallpapers:4.3
kde-base/kdebase-cursors:4.3
kde-base/kdebase-data:4.3
kde-base/kdebase
2009/11/26 James wirel...@tampabay.rr.com:
Alan McKinnon alan.mckinnon at gmail.com writes:
grep kde /var/lib/portage/world
only kde-meta in there
emerge -a --depclean
yep, just making sure as I thought there might be a
very special syntax to remove all kde 3.5.*
I used revdep
4.14.3-r1:4/4.14::gentoo USE="alsa
> >>> handbook (- aqua) -canberra -debug -pulseaudio"
> >>> [blocks b ] kde-apps/kmix:4 ("kde-apps/kmix:4" is blocking kde-
> >>> apps/kmix-15.12.3)
> >>> [ebuild NS] kde-apps/kdemultime
gt;> [uninstall ] kde-apps/kmix-4.14.3-r1:4/4.14::gentoo USE="alsa
>>>>> handbook (- aqua) -canberra -debug -pulseaudio"
>>>>> [blocks b ] kde-apps/kmix:4 ("kde-apps/kmix:4" is blocking kde-
>>>>> apps/kmix-15.12.3)
>>&g
profile and try something like emerge -Cp kde-meta
then there are lots of warning messages about how I'm removing parts
of @system. It's unlikely (in my mind anyway) that anything would be
removed that stops one from doing the 4.6 emerge, but if one goes this
way they should look very carefully at what's
On Thu, 26 Jul 2007 19:01:15 + (UTC), James wrote:
Where do I read about what all is in xorg-x11 versus xorg-server(which
is all that kde-meta needs?)? What exactly does kde-meta needs and
such
emerge kde-meta -pv should show you all that KDE needs.
--
Neil Bothwick
Top Oxymorons
On 6/2/06, Mick [EMAIL PROTECTED] wrote:
Hi All,
Apologies if this has been asked before. I uninstalled my monolithic
KDE and am ready to install the split KDE ebuilds. I want to install
everything except toys, games and educational packages. Since the
DO_NOT_COMPILE is not meant to be used
Sean
Looks like your trying to mix 'kde' (monolithic) and kde-meta ebuilds
(split). Trying emerging kde-meta 4.0.
signature.asc
Description: PGP signature
Helmut Jarausch jarau...@igpm.rwth-aachen.de writes:
Hi,
I'd like to upgrade all my installed package from, say, kde-base/* .
emerge -u kde-base/kde-meta doesn't work unfortunately.
Is there something easier than
Try emerge -u $(qlist -IC kde-base/)
/kde-base/ | grep meta
Thanks. Last question:
Is emerging kdebase-meta meant to pull in 45 packages, or are there
any old kde apps in my system pulling them in as I am trying to emerge
my new split KDE?
From the log:
===
1149285323: *** emerge --update --deep
kldap
> * These packages depend on kldap:
> kde-apps/incidenceeditor-17.12.3 (>=kde-apps/kldap-17.12.3:5)
> kde-apps/kdepim-meta-17.12.3 (>=kde-apps/kldap-17.12.3)
> kde-apps/kmail-17.12.3 (>=kde-apps/kldap-17.12.3:5)
> kde-apps/kmail-account-wizard-17.12.3 (>=kde-app
Well, not Plasma's but mine for sure. I have been chasing my tail trying to
reverse engineer processes/services/applications I do not want auto-running on
a fresh Plasma installation and I'm fast losing the will to live.
I've installed plasma-meta plus some kde-apps meta packages as follows
Currently running KDE 3.3. I get the following:
[EMAIL PROTECTED]:/# emerge --pretend kde-meta
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[blocks B ] =kde-base/kdebase-3.4* (is blocking
kde-base/kscreensaver-3.4.1)
[blocks B ] =kde-base
1 - 100 of 1441 matches
Mail list logo
