optimism :)
If you emerge kde-meta, you'll have everything that the monolithic kde
ebuild gave you, just in manageable bite-sized chunks.
Hmph. You call 300 separate ebuilds manageable? I suppose it is if
you meta them in as a chunk.
It's also manageable in that you can manage what gets
with modular X.
Maybe what is needed is an enhancement to portage to allow the removal
of a meta-package to (optionally) also remove the 'real' packages
which it caused to be installed.
u think about this.
new system, no gui installed.
I install kde-meta, which installs xorg-x11
it caused to be installed.
NR
NR u think about this.
NR
NR new system, no gui installed.
NR
NR I install kde-meta, which installs xorg-x11 as a dependency.
NR
NR I decide I want gnome, I install gnome which doesn't install xorg,
NR because it is already installed.
NR
NR I decide I do not want
in /etc/make.conf. If emerge want it,
when I do the following command:
# emerge kde-meta
After this command, emerge tell me that I must to use e.g. X, so I add a
given flag to USE=X jpeg png -debug etc. to file /etc/make.conf.
No, because I put it to /etc/make.conf, not as you show all in one
misunderstanding?
Yes and no.
Yes, because I add a given flag to USE in /etc/make.conf. If emerge want it,
when I do the following command:
# emerge kde-meta
After this command, emerge tell me that I must to use e.g. X, so I add a
given flag to USE=X jpeg png -debug etc. to file /etc
/linux/arch/10.0/desktop/kde and rebuild. Alan and Neil's
idea of a set of the meta-packages you want sounds good to me too.
Then you'll really have a clean system.
You will have whatever system the profile maintainer thinks the
average user should have, bloated to whatever degree said
On Sunday 07 August 2011, john wrote:
Hello,
I am trying to emerge kde-meta but getting the following error
message
Calculating dependencies... done!
Traceback (most recent call last):
File /usr/bin/emerge, line 43, in module
retval = emerge_main()
File /usr/lib64/portage/pym
Francesco Talamona wrote:
On Sunday 07 August 2011, john wrote:
Hello,
I am trying to emerge kde-meta but getting the following error
message
Calculating dependencies... done!
Traceback (most recent call last):
File /usr/bin/emerge, line 43, in module
retval = emerge_main
are still around. There is a list of the monos in
the url I posted in another mail to this thread.
Would it be possible to modify the kde-meta eclass so that a split vs
monolithic block gave a more informative error message. Even a generic
message pointing to that URI would be a great help
trying to figure out what to put in those package.* files
to make something work. Everytime i figure it out, they change
something. Reminds me of that qpkg or whatever it was they took away.
I plan to use the kde-meta thing, like I have now. I tried a command
earlier that was supposed
.
basically kde (can't speak to gnome, don't care for it) is broken
into lots of ebuilds. I personally did an emerge kde-meta, because I
use the full-blown kde. but there's also smaller bits you can install.
Always do an emerge packagename -pv first, as it will evaluate your
USE flags and tell
On Friday 22 June 2007, Dale wrote:
I'm not using noatun, it appears that that is what KDE is using or
something. See this:
[EMAIL PROTECTED] / # equery depends kdemultimedia
[ Searching for packages depending on kdemultimedia... ]
kde-base/noatun-plugins-3.5.7 (~kde-base/kdemultimedia
use autounmask for?
No version of kde is masked here.
Helmut.
At first portage gave me errors about things being masked/keyworded.
So, I figured out it was trying to upgrade the kde-meta and used
autounmask to make sure they were all available. After that, it just
started updating. So
autounmask to unmask it. I use
this command:
autounmask kde-base/kde-meta-4.5.1
Easier way would be to install the KDE overlay and use the etc files
provided in the Documentation directory for unmasking and so on. If
you want to stick to KDE ebuilds from portage proper, you could copy
the etc
dependencies of @system, but they will
also be dependencies of @world, because you have emerged kde-meta, so
either way they would be on your system.
There is nothing wrong with your system, it is doing exactly what you
told it to with your USE flags, and the kde flag is not the culprit
anyway as emerge
of. This is the error I get:
[blocks b ] kde-base/kde-meta:4.3[-kdeprefix]
(kde-base/kde-meta:4.3[-kdeprefix] is blocking kde-base/kde-meta-)
[blocks B ] app-arch/lzma-utils (app-arch/lzma-utils is blocking
app-arch/xz-utils-)
[blocks B ] app-arch/xz-utils (app-arch/xz-utils is blocking
app-arch
On 17 Dec, Dale wrote:
I'm trying to get KDE 4 where I can use it so I used the layman to get
the latest. Anyway, I seem to have ran into a Block, may not be related
to KDE4 tho, that I just can't make sense of. This is the error I get:
[blocks b ] kde-base/kde-meta:4.3[-kdeprefix
).
I use xfce, so that shouldn't be a problem, right? I've tried emerge
-C gnome and emerge -C kde, but the gnome line only unmerged the final
gnome package, and the kde line didn't work at all (I'm thinking it's
called kde-meta now), but unmerging kde-meta only unmerged the final kde
package
tried emerge
-C gnome and emerge -C kde, but the gnome line only unmerged the final
gnome package, and the kde line didn't work at all (I'm thinking it's
called kde-meta now), but unmerging kde-meta only unmerged the final kde
package. How do I do this?
I would recommend using emerge -p
be helpful but failed to start due to kde related issues.
As for the new plasma stuff, I have almost all possible kde packages
updated to 5.x (unstable), with the exception of kdm, kwin, settings and
several others. My emerge of plasma-meta replaced these and additionally
installed 78 packages
Alan McKinnon wrote:
On Sunday 20 January 2008, Dale wrote:
H, I get this blocker:
[blocks B ] =x11-libs/qt-4.4_rc:4 (is blocking
x11-libs/qt-core-4.4.0_rc1)
Is unmerging qt a good idea?
Yes, looking in the ebuild, qt-4.4 seems to be organized as a meta
package
On Sunday 20 January 2008, Uwe Thiem wrote:
On 20 January 2008, Alan McKinnon wrote:
Hi all,
My portage-fu is apparently up the creek. Again.
Trying to emerge kde-4.0.0, I get this:
==
nazgul ~ # emerge -av kde-meta
These are the packages that would be merged
Daniel Pielmeier wrote:
Installed packages with a version not in the database (or masked):
As it says this apps are either not in the database or masked.
kde-base/kdeaddons-docs-konq-plugins-3.5.9 masked
kde-base/kdeaddons-kfile-plugins-3.5.9 masked
kde-base/kdeaddons-meta-3.5.9 masked
sys
kdebase-kioslaves? Why? With KDE, either you go
for the all-in-one-big-honking-package approach (kdebase proper), or you
cherry pick what you need from the split packages (the kdebase-* packages).
Same goes for the other kde core packages. If you want to switch from one
big package to several small
of the
needed functions are missing.
Filters transform gamma brightness blur Desktop... all missing. Or
well hidden.
I'm guessing I need to install some more of kde. So I thought I might
kill a fat hog by emerge -v -p kdebase/kde-meta.
On the contrary this produces a large nasty looking list of pkgs
On Wednesday 28 September 2005 07:04, Michael Kjorling wrote:
On 2005-09-28 06:52 -0500, [EMAIL PROTECTED] wrote:
A stage 3 will not install X, unless you do emerge something after
install that requires Xlike when I did an emerge kde-meta...that got
X installed, then kde and xdm, etc
working faster, then you can
optimise at your leisure.
But, they say you can optimize your system when you use 1st or 2nd stage...
Is it possible optimize after using 3rd stage for installation?
askar
you want to emerge kde-meta, not emerge kde. The binary packages on the
latest CD use the new
.* files
to make something work. Everytime i figure it out, they change
something. Reminds me of that qpkg or whatever it was they took away.
I plan to use the kde-meta thing, like I have now. I tried a command
earlier that was supposed to generate it but it created a blank file for
me. :/
Thanks
of kde-meta? I don't know, equery list
kde then poke them in one by one. Would that let it leave kate and
kdelibs where it is without masking all of kde?
Thanks for the reply though. At least I can open the file and read it
and it is not just me having this problem.
Dale
understand the difference between kdemultimedia and
kdemultimedia-meta.
Read this:
http://www.gentoo.org/doc/en/kde-split-ebuilds.xml ;-)
Regards, Elias P.
--
A really nice number:
09:F9:11:02:9D:74:E3:5B:D8:41:56:C5:63:56:88:C0
signature.asc
Description: This is a digitally signed message part.
directories in /usr/share.
Hi Volker,
I rebuild kde-meta package and find out that I have not add consolekit
to default boot level. After I have done that everything is fine.
Thanks
Hung
Hi I am trying to run revdep-rebuild and it gets to the emerge stage and i get
this
!! All ebuilds that could satisfy kde-base/kdelibs:3.5 have been masked.
!!! One of the following masked packages is required to complete your request:
- kde-base/kdelibs-3.5.10-r6 (masked by: package.mask)
/usr
: - kde-base/kdelibs-3.5.10-r6 (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Samuli Suominen ssuomi...@gentoo.org (31 Dec 2009)
# Doesn't compile anymore with Autoconf = 2.64, wv2 = 0.4.0,
# several open security bugs, ...
#
# Replaced by app-office/koffice-meta-2.1.0
#
# See
/kfilereplace-4.5.2 [installed])
(dependency required by kde-base/kdewebdev-meta-4.5.2 [installed])
(dependency required by @selected)
(dependency required by @world [argument])
So it looks as though I at least can't get rid of it.
--
Rgds
Peter. Linux Counter 5290, 1994-04-23.
On Thu, 23 Jun 2011 23:06:28 +0200, Alan McKinnon wrote:
I do similar, except I'm even more of a control freak than you, so
my kde4 set contains onl;y a couple of meta-packages, the rest it
individual packages.
% wc -l /etc/portage/sets/kde4
83 /etc/portage/sets/kde4
Sad, I know
On 09/11/2011 03:17 AM, Peter Humphrey wrote:
Hello List,
I was getting fed up with the bloat and maintenance headaches with my setup,
which used the kde desktop profile and emerge kde-meta.
So I formatted the root partition and installed from scratch. This time I
kept the standard
have anything to do with cd playback.
Since you are trying to use KDE apps to play CDs you ought to check
that you
have installed:
kde-base/kdemultimedia-meta
kde-base/kdemultimedia-kioslaves
Yes, have both installed. :-)
involved:
dev-db/virtuoso-server-6.1.6
kde-base/kde-meta-4.10.5
What column in htop shows that number?
top, htop, and all their friends do not display what most people assume
they display. Modern OSes (for more than a decade now) manage memory in
a way that makes it impossible to answer how much
did you go about overcoming this?
I also have dev-qt/qtcore-4.8.5-r2 and some other qt packages installed
but I had no problems with that.
I'm on gentoo stable (not ~amd64) and I don't use KDE.
I only use some KDE apps, not the full meta. There seems to be a problem
with dev-qt
you go about overcoming this?
I also have dev-qt/qtcore-4.8.5-r2 and some other qt packages
installed but I had no problems with that.
I'm on gentoo stable (not ~amd64) and I don't use KDE.
--
Regards
wabe
I only use some KDE apps, not the full meta. There seems
same thing as installing a wallpapers package. It
looks in this case as though setting the flag will cause packages to be
installed as part of *-meta, but I dare say it's just a convenience to save
one operation.
> 'layman -L' finds no kde-sunset.
Google suggests it's in git nowadays.
>
On Sat, May 30, 2020 at 11:21 AM Grant Edwards
wrote:
>
> On 2020-05-30, Peter Humphrey wrote:
>
> > I masked the latest version of plasma-meta, 5.18.5, [...]
>
> > Is this going to be policy in future? Bloat the machine up with bells
and
> > whistles that a
On Saturday 10 December 2005 10:47, Harry Putnam wrote:
First off, this is an install from scratch.
While your comment sounds smart, this really only puts off doing it
later.
^^ huh?
And the mindnumbing confusion of what parts of kde do what.
I'm not compiling kde-meta either, but I've
I don't think it makes a useful measure
of anything. And KDE-meta isn't much better these days either.
Yesterdays sync brought in 3.5.6 and 3 or 4 other bits and pieces,
which I started at 1am this morning. It's just finished now at 1pm
- 12 hours!
KDE is in so far better as it doesn't
by x11-libs/qt-qt3support-4.5.2 [ebuild])
(dependency required by kde-base/kteatime-4.2.4 [installed])
(dependency required by kde-base/kdetoys-meta-4.2.4 [installed])
(dependency required by kde-base/kde-meta-4.2.4 [installed])
OK, let's try:
adding qt3support to qt-core wants qt3support for qt-gui
/qt-core-4.5.2 (Change USE: +qt3support)
(dependency required by x11-libs/qt-qt3support-4.5.2 [ebuild])
(dependency required by kde-base/kteatime-4.2.4 [installed])
(dependency required by kde-base/kdetoys-meta-4.2.4 [installed])
(dependency required by kde-base/kde-meta-4.2.4 [installed
)
[ebuild N] virtual/mta-0
[nomerge ] kde-base/kde-meta-4.4.5
[nomerge ] kde-base/kdemultimedia-meta-4.4.5
[nomerge ] kde-base/dragonplayer-4.4.5
[nomerge ]media-libs/xine-lib-1.1.19
[nomerge ] media-libs/libmng-1.0.10
[ebuild R ] virtual/jpeg
dependencies ... done!
[nomerge ] app-admin/sudo-1.7.4_p5
[nomerge ] virtual/mta-0
[ebuild N ] mail-mta/ssmtp-2.62-r8 USE=ipv6 ssl -maxsysuid (-md5sum)
[ebuild N ] virtual/mta-0
[nomerge ] kde-base/kde-meta-4.4.5
[nomerge ] kde-base/kdemultimedia-meta-4.4.5
[nomerge
statement. But the point is my
profile turns on R by default so just by emerging kde-meta I end up with
the GCC fortran compiler and packages that require a fortran compiler.
And if the fortran use flag was turned off (either by changes on ~x86 or
if I turn it off myself) then I get build failures
for dropping Lcms:0 .
Unfortunately, Kde-Sunset appears to require Lcms:0 for Libmng:0 ,
which is required by Qt-Meta:3 which aren't included in Kde-Sunset
itself. For now, I can simply ignore the warning, but it looks
as if it wb no longer possible to install Kde-Sunset on a new machine.
qt-meta
I've seen gnome-base/gnome-common pulled in on more than one systems, all of
which have USE="-gnome" set:
# emerge -uaNDvt world
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
[nomerge ] kde-apps/kdebase-meta-17.08.3:5::gento
On Thursday 01 March 2007, Bo Ørsted Andresen [EMAIL PROTECTED] wrote
about 'Re: [gentoo-user] problem emerging kde-meta':
On Thursday 01 March 2007 22:54:43 Boyd Stephen Smith Jr. wrote:
Your problem is that you are trying to mix them. That is difficult or
impossible and is AFAIK
-package pull in basically the same packages.
Unmerge the set, emerge kde-meta then do a depclean to catch any
stragglers.
I would just delete the set from the world_sets file, then emerge
kde-meta, then depclean... much easier than unmerging everything and
recompiling it.
Sorry
I thank the four of you for the insight I learn more in 5 mins then I did in an
afternoon,I have two last question tho
> As a example, if you want a
> full KDE install, you just emerge the kde meta package and it gets
> recorded in the world file. The emerge command will take ca
.
Do as previously suggested and use individual meta packages instead of
the all-encompassing kde-meta, or use a mixture of meta and individual
packages (that is what I do).
If you just want to omit a couple of packages, try package.provided. This
is not what it is meant for, but I have used
; back, at least for now.
>
> I know, had to copy a meta-ebuild ( kdegraphics-meta ) into my local
> overlay and modify it to pick ksnapshot though. As the later version
> only allows Spectacle.
I don't use the meta packages, preferring to define my own set with the
packages I want, so I
.
If you've removed kde-meta, I'm not surprised.
It's not (mainly) kde packages that show up there. It's:
I'm surprised these show up from --depclean:
app-admin/logrotate
app-arch/sharutils
app-crypt/hashalot
app-crypt/mhash
app-text/psutils
dev-libs/glib
dev-libs/lzo
dev-libs
) and place it in /usr/portage/distfiles
* If you find the file on the download page replaced with a higher
* version, please report to the bug 67266 (link below).
* If emerge fails because of a checksum error it is possible that
* the upstream release changed without renaming. Try downloading the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am trying to udate kde-meta (actually, I think it never completely
installed, but I'm doing an update now) and it won't get past the very
first part, that of kde-base/libkpimidentities-3.5.8, because it gets this
error:
libsandbox: Can't resolve
seem to like the latest portage. I'm not complaining and I
know I am running unstable packages. Just thinking he may not know that
his code just got borked. :-O
I eagerly await the day one can keyword/unmask kde-meta and it
automatically unmasks all its friends. I'm not sure how good that day
about other GUI's?
What does it matter? They are only dependencies of @system, but they will
also be dependencies of @world, because you have emerged kde-meta, so
either way they would be on your system.
There is nothing wrong with your system, it is doing exactly what you
told
dependencies of KDE. Emerge the KDE apps or meta packages you want and let
portage take care of dependencies.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
:10 sets
root@fireball / #
I created the package.* ones and I think I did the sets one too. I
haven't messed with the others tho.
I wonder if the devs know about all this? Is this something they should
know about? Is this unique to me? I have KDE installed by using the
kde-meta but surely
;
> The above constraints are a subset of the following complete expression:
> python? ( python_targets_python2_7 ) qt5? ( !qt4 ) kde? ( qt4 )
And this is the helpful gigantic USE expression, all of which must be
satisfied to install mlt. The bit above this shows just the part that is
I would strongly, STRONGLY discourage you from creating your own meta
package. There are very few meta packages in the tree (in the scheme
of things) for very good reasons, they take one hell of a lot of
maintenance. They're really only there for things like kde, where you
might just want a bare
- and there are several versions available in both branches. On
my box, I have qt-3.3.8-r4 installed in the qt:3 SLOT and qt-4.3.2.-r1
in the qt:4 SLOT. So far so good. Now look at kde:
* kde-base/kde-meta
Available versions:
(3.5) 3.5.8 (~)3.5.9
(kde-4) {M}(~)4.0.1 {M}(~)4.0.2
On Mon, Feb 2, 2009 at 12:21 PM, Roy Wright r...@wright.org wrote:
Neil Bothwick wrote:
On Mon, 02 Feb 2009 11:14:34 +0100 (CET), Helmut Jarausch wrote:
nice -19 emerge -j4 --buildpgkonly kde-base/kde-meta
but it takes next to no time instead of hours and
hasn't build the binary packages
by default?
It's not enabled in the profile, it's enabled in the ebuild:
IUSE=debug ps +R
and likely for the same reason there's a scary warning. If
you're installing cantor, because you plan to use it (and
not because kde-meta is a bloat monster), you need one of
the two backends to make
/kdepim-meta
Available versions: 3.4.1 ~3.4.2 3.4.3 ~3.5.0
Installed: none
Homepage:http://www.kde.org/
Description: kdepim - merge this to pull in all
kdepim-derived packages
* kde-base/kdesu
Available versions: 3.4.1 3.5.0
Installed
~3.5.0-r4
Installed: none
Homepage:http://www.kde.org/
Description: KDE graphics-related apps
* kde-base/kdepim-meta
Available versions: 3.4.1 ~3.4.2 3.4.3 ~3.5.0
Installed: none
Homepage:http://www.kde.org
ed:
> > kde? ( qt4 )
>
> This is the actual problem, According to the ebuild, if you set
> USE="kde", then you also need USE="qt4". Your USE has qt5 enabled, and
> that's the problem.
>
> Presumably, mtl does not yet support KDE with Qt5
> >
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir Rusinov wrote:
On 3/14/08, *Chuck Robey* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am trying to install kde-meta. I have been fixing my USE variables
as I
and 3.4 with one or three
collective
names?
You still have kde-3.2 installed?? You've been around Gentoo longer
than I have, that's for sure!
In any case:
emerge --prune kde kde-meta
emerge --pretend depclean
emerge depclean
Even if I do this, there remain some current complaints from revdep
/portage/world) tidy, simply deleting
all
lines with KDE3 packages and running emerge -a --depclean will take care of
it.
You *do* keep your world file tidy, don't you? :P
That would be the easiest method. If you use the kde-meta package like I do,
just remove the one for KDE 3 and let
On Wednesday 12 March 2008, Alan McKinnon wrote:
On Wednesday 12 March 2008, Uwe Thiem wrote:
I have 3.5 as monolithic and 4.0 meta. What concerns me is that
adding xcomposite will not re-emerge anything from 4.0 - and
there is where I need/want it.
OK, I see what you mean. Try
, they
are not. For example, none of the lib* packages should be there.
I see (I think). Please bear with me while I am catching up: the
script will individually emerge every KDE component as opposed to the
original meta packages which brought in with them their dependencies.
The latter would not have been
not installed how can it be running (hung)?
I've tried all sorts of things to fix this and nothing
works, including revdep-rebuild...
Are you using the monolithic or split ebuilds for kde?
got me on this one. Not Sure? I'd guess both is a bad idea?
That is, did you emerge kde or emerge kde-meta
of knowing which package provided a file
and if everything else that is necessary is actually on the system.
You have run slap bang into the infamous kde-meta problem :-)
Solution here:
http://www.gentoo.org/proj/en/desktop/kde/kde-split-ebuilds.xml
Beware: fixing this is relatively
and start over. Does anyone know a simple way (maybe a
script) to do this? As far as I'm concerned, I'd really like to unmerge
everything installed from the overlay.
Unmerge the packages you specifically merged (kde-meta:4.1 perhaps;
whichever packages are in your world file) then run depclean
Alan McKinnon wrote:
On Sunday 05 October 2008 20:16:55 Neil Bothwick wrote:
On Sun, 05 Oct 2008 20:08:23 +0200, b.n. wrote:
Could you share your relevant package.mask and package.keywords, for
the laziest of us? :)
emerge autounmask
autounmask kde-meta
. This probably isn't a specific Gentoo issue.
It *could* be a KDE issue, but I haven't done anything to KDE. When I
installed KDE in September, I emerged kde-meta. I don't recall if
there have been updates since then, but I know that I could shutdown
or restart using the menu selection and no changes were
-base/kdebase-meta-4.3.1 (=kde-base/keditbookmarks-4.3.1:4.3[kdeprefix=])
It's utter madness, but with free software there are alternatives,
which I have started to adopt (Fluxbox, Thunar, Terminal).
Unfortunately, Thunar is as simple as Nautilus (or even more basic). They
don’t nearly come close
])
(dependency required by kde-base/kdepimlibs-4.3.1 [ebuild])
(dependency required by kde-base/kdnssd-4.3.1 [ebuild])
(dependency required by kde-base/kcontrol-4.3.1 [ebuild])
(dependency required by kde-base/kdebase-meta-4.3.1 [ebuild])
(dependency required by world [argument])
Result of 'eix
/akonadi-server-1.2.1 [ebuild])
(dependency required by kde-base/kdepimlibs-4.3.1 [ebuild])
(dependency required by kde-base/kdnssd-4.3.1 [ebuild])
(dependency required by kde-base/kcontrol-4.3.1 [ebuild])
(dependency required by kde-base/kdebase-meta-4.3.1 [ebuild])
(dependency required by world
(Change USE: +mysql)
(dependency required by app-office/akonadi-server-1.2.1 [ebuild])
(dependency required by kde-base/kdepimlibs-4.3.1 [ebuild])
(dependency required by kde-base/kdnssd-4.3.1 [ebuild])
(dependency required by kde-base/kcontrol-4.3.1 [ebuild])
(dependency required by kde
On Tuesday 27 October 2009 18:13:29 James wrote:
Hello,
I have several workstations on kde4, mostly 4.2.4 or 4.2.x.
I'm looking for a clean, easy, unattended method to upgrade
about a dozen systems to kde 4.3.x (Or KDE 4 stable only). I'm
not sure what the latest stable kde4 version
--- On Sat, 2/1/10, Volker Armin Hemmann volkerar...@googlemail.com wrote:
From: Volker Armin Hemmann volkerar...@googlemail.com
Subject: Re: [gentoo-user] revdep-rebuild and kde-base/kdelibs:3.5
To: gentoo-user@lists.gentoo.org
Date: Saturday, 2 January, 2010, 12:05
On Samstag 02 Januar
happy with ~amd64 on @system, but want to build
the stable version of gnome or kde. How do I get it? Since gnome-2.26
worked yesterday I tried masking =gnome-2.28. emerge -DuN gnome.
Portage then didn't try to emerge the meta-package but doesn't take
all of gnome back to 2.26. There's no point trying
unsupported by
KDE. Get used to having it enabled.
Tis true, if you try to build kdepim-meta it'll go into a fit, because
some package therein won't build without semantic-desktop. I had to
put mine back.
--
Regards,
Mick
On Sun, Jun 17, 2012 at 4:42 AM, Pandu Poluan pa...@poluan.info wrote:
So, while we're meta-discussing Linus' rant on Gnome3, here's an article
from TechRadar exploring the usability of the leading Linux desktop
environments.
http://www.techradar.com/news/software/operating-systems/whats
-plugins-meta-0.10-r8:0.10 vorbis
So maybe KDE is pulling in something.
I guess I will continue using
claws-mail,since i only send text emails.
Thanks for new options i was not aware.
nstalling knotify:4 I suddenly got desktopn messages from KMail
> again.
>
> > A user complained that new messages no longer create a popup.
>
> Seems to match the error log.
>
> Cheers,
> Jörg
I think both kwallet:4 and knotify:4 should have been retained as d
-4.3.50_pre20090520 (0)
r...@smoker / #
I'm about ready to unmerge kde-meta:4.3 and then do a depclean. That
would fix it. lol
Ideas?
Dale
:-) :-)
Hello,
I'm trying to emerge kde-meta. Before I have removed about every kde
package to start as clean as possible. The merge fails here:
Applying xdelta: kdeaddons-3.4.0-3.4.1.tar.xdelta
...
/usr/qt/3/bin/moc ./kfile_cert.h -o kfile_cert.moc
/bin/sh ../../libtool --silent --mode=compile --tag
Yuri K. Shatroff wrote:
> Hi guys,
>
> 12.04.2016 08:38, Dale wrote:
>> Howdy,
>>
>> Well, I went and did it.
>
> So I went and did it, too.
> Thank gods I made a backup. After emerging plasma-meta which wasn't
> too easy because of dependency hell with eg ne
as to how to fix this schema color issue on the newly
installed (livedCD 2006.1) (K8) system are most welcome. Initially,
I performed a networkless (kde-less) install. Since then I have
emerged kde-meta and all seems fine, except this schema colors
in my kde terminal sessions.
Is this a bug?
James
a basic KDE session :-)
I suspect you might not have the control centre and it's modules at all, so
you don;t have the background settings daemon thingy that controls the look
and feel of all of kde.
Edit ~/.kderc to set defaults you like
Or you could install the kdebase-meta to get everything
. I'm running kde-meta 4.3.3
It's the kde screen where you put your login and passwd.
It flashes for a second or 2, like the passwd is accepted, but
kde cannot start.
If I do not auto start kdm via rc-update, then I can log in as a user
and X starts (twm?).
I can also ssh into the system so
Joost Roeleveld wrote:
Are the usual suspects running?
Like dbus and consolekit?
Yep. I made sure dbus and consolekit was up a running. I even made
sure the process was running, just to be for sure and for certain. ;-)
which kde-package(s) did you emerge?
I use kde-meta
*do* keep your world file tidy, don't you? :P
That would be the easiest method. If you use the kde-meta package
like I do, just remove the one for KDE 3 and let --depclean do its
thing. It should get all of it.
I actually don't touch the world file, and just do the 'emerge world
-vuDNa
801 - 900 of 1441 matches
Mail list logo
