rameworks/kf-env-4
> =kde-frameworks/kglobalaccel-5.32.0
> # required by kde-plasma/ksshaskpass-5.9.3::gentoo
> # required by kde-plasma/plasma-meta-5.9.3::gentoo
> # required by @selected
> # required by @world (argument)
> # /etc/portage/package.mask/kde:
>
I have a problem getting rid of KDE (those meta package might be easy to
install/upgrade but getting rid of them is not easy).
When I run emerge -uDNav world I get:
The following USE changes are necessary to proceed:
#required by kde-base/libkonq-4.7.3, required by kde-base/kdepasswd-4.7.3
2009/10/25 Alan McKinnon alan.mckin...@gmail.com:
On Sunday 25 October 2009 22:19:11 Mick wrote:
# emerge -uatDv world
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
[nomerge ] kde-base/kdepim-meta-4.3.1 USE=(-kdeprefix)
[ebuild N
On Tuesday 06 December 2005 22:45, Gerhard Hoogterp wrote:
As it seems xmlto needs the latest libxlst 1.1.15 and DOESN'T have a
dependency for it.
As I try to emerge kde-meta I run into the following error:
/usr/kde/3.5/bin/meinproc --check --cache index.cache.bz2 ./index.docbook
On AD 2007 June 15 Friday 08:55:40 AM +0200, Alexander Skwar wrote:
On my system, I don't use a modem and don't intend to ever
do so. Because of this, 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, which will pull
On Fri, 15 Jun 2007 05:10:00 -0500, Boyd Stephen Smith Jr. wrote:
The kde-meta package is meant to replace the kde package. The is no
advantage (and without a workable confcache, at least one disadvantage)
to running split ebuilds.
What about the need to recompile only one part of KDE when
Trying to upgrade to qt 4.5.2:
kde4 wants qt3support for qt-core:
x11-libs/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
])
(dependency required by kde-base/kdepim-meta-4.5.95 [ebuild])
(dependency required by kde-base/kde-meta-4.6.2[semantic-desktop]
[installed])
(dependency required by @selected [set])
(dependency required by @world [argument])
root@fireball / #
So, it is not masked or keyworded, it just plain
/removing lines/individual USE flags I found that the doc flag was
the source of the error:
USE=kde X qt4 doc emerge -pv kde-meta
These are the packages that would be merged, in order:
Calculating dependencies . . .. done!
!!! Error: circular dependencies:
('ebuild', '/', 'kde-base
and the meta-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.
On Thu, 29 Oct 2009 11:45:54 -0500, Paul Hartman wrote:
Are there any tricks to remove all of kde4, or do
I have to do it manually?
The set and the meta-package pull in basically the same packages.
Unmerge the set, emerge kde-meta then do a depclean to catch any
stragglers.
I
/portage/kde-base:kscd-4.7.2:20111007-075837.log'
*** Resuming merge...
These are the packages that would be merged, in order:
Calculating dependencies... done!
* emerge --keep-going: kde-base/kdemultimedia-meta-4.7.2 dropped due to
* unsatisfied dependency.
* emerge --keep-going: kde-base/kde-meta
On Tuesday 06 February 2007, Dale wrote:
I don't understand portage and ebuilds well enough to do that. How
about this. Is there a way to just tell emerge to emerge each
separate package and get rid of kde-meta?
kde-meta is, well, as meta package. All it does is tell portage to
emerge all
Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
On Friday 15 June 2007, Alexander Skwar [EMAIL PROTECTED]
Yep. You get kde-meta or individual kde packages or you get your own
ebuild that depends on a number of KDE packages. The Gentoo developers do
quite a bit of work just to give us kde
to easily define what's in a set if the standard ones don't suit your needs.
OK, I got it, use SETS instead of kde-meta.
Where do I read up on using SETS?
I see set in the emerge manpage, but it seem, brief.
How do you use the default sets when upgrading to
kde-4.2.x?
Any examples
On Mon, Dec 22, 2008 at 04:20:25AM +0200, Penguin Lover Nikos Chantziaras
squawked:
I'm not using -meta packages. Many packages they pulled in was stuff I
don't wanted (like PIM). I emerged KDE packages one-by-one and went with
what got pulled in as dependencies.
Uh.. then what exactly
On 6/16/07, Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
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
On Monday, 24 June 2019 21:40:07 BST Mick wrote:
> According to the current wiki page these days the kde-meta has been
> replaced with plasma-meta. This is how I have configured plasma-meta:
>
> Installed versions: 5.15.5(5)(12:58:00 14/06/19)(bluetooth browser-
> in
scheduled for merge)
>=kde-apps/libksane-16.04.1 required by
(kde-apps/kdegraphics-meta-16.04.1:5/5::gentoo, ebuild scheduled for merge)
I'm not so worried about the procps thing right now, although it keeps
popping up. The libksane one has me puzzled. Here is some info on the
packages t
On 12/15/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Well you might think all that would be necessary is to keyword either:
kde-base/kdebase ~x86
kde-base/kde-meta ~x86
kde-base/kde ~x86
Nope, you have to keyword-accept the dependancies also...
What happens is emerge runs
On Sat, 17 Dec 2005 21:41:26 -0600
Samir Faci [EMAIL PROTECTED] wrote:
Nick Rout wrote:
I see a lot of people seem to have upgraded to kde 3.5.
I am currently running kde 3.4.1 (installed via kde-meta) and stable is
3.4.3. However reports seem to be that 3.5.0 seems good enuf to work
but it is one heck of a list. It's 6 pages
long in OOo.
emerge unmerge kde-meta and emerge -a depclean
(Since you have such a long package list I assume you installed via split
ebuilds, otherwise replace kde-meta with kde).
HTH...
Dirk
--
Dirk Heinrichs | Tel: +49 (0)162 234
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
On my ~x86, I had to add:
~app-misc/strigi-0.5.11
to etc/portage/package.unmask
On 4/8/06, Pete Pardoe [EMAIL PROTECTED] wrote:
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
No you haven't. package.keywords doesn't get applied
have akode installed. /var/db/pkg
contains only the packages you have installed whereas /usr/portage contains
everything. equery --list outputs only what you have installed by default.
Finally you should know that because kde is slotted you do not have to remove
kde-3.4 before installing kde-meta
On Sat, 09 Apr 2016 11:12:51 +0100, Mick wrote:
> I noticed to day that Plasma 5 is now stable, which means I will soon
> have to deal with it. I run a number of boxen with Gentoo on them.
> Some of them do not run a full KDE desktop, only selected KDE apps,
> some KDE meta packag
On Thursday 01 March 2007, Turi Tropea [EMAIL PROTECTED] wrote
about 'Re: [gentoo-user] problem emerging kde-meta':
Bo Ørsted Andresen ha scritto:
Just unmerge kdebase and you should be able to proceed...
the kde related packages was installed by beryl and aquamarine...so if
i unmerge them
/var/portage/kde-base/*
/var/portage/kde-base/kdegraphics-meta/kdegraphics-meta-4.3.0.ebuild: =kde-
base/thumbnailers-${PV}:${SLOT}[kdeprefix=]
/var/portage/kde-base/kdegraphics-meta/kdegraphics-meta-4.3.1.ebuild: =kde-
base/thumbnailers-${PV}:${SLOT}[kdeprefix=]
So I'll bet that you have
>
> !!! All ebuilds that could satisfy "kde-apps/kdebase-runtime-meta:5"
> have been masked.
>
> !!! One of the following masked packages is required to complete your
> request:
>
> - kde-apps/kdebase-runtime-meta-16.04.2::gentoo (masked by:
> pa
of the kde packages
on a (kde-meta) system? emerge kde-meta only rebuild the
meta package itself
emerge -avuND world
If that doesn't pull in the missing bits, you have USE flags and/or
package.mask getting in the way.
equery depends might help, but it's only accurate for stuff you already
:
union, intersection, difference plus a few others.
@set1+@set2/@set3 reduces to:
all the elements of set1 and set2 without the elements that are in set3
(/ is difference).
As an example, assume portage ships two sets @kde and @kdedev:
@kde
kdeadmin-meta
kdebase-meta
') pulled in by
=kde-base/phonon-xine-4.1.4:4.1 required by ('ebuild', '/',
'kde-base/kdebase-meta-4.1.4', 'merge')
kde-base/phonon-xine:4.1[xcb] required by ('ebuild', '/',
'kde-base/dragonplayer-4.1.4', 'merge')
For more information about Blocked Packages, please refer to the following
u want, they have
> deps on the libs they need. Whatever they pull in is required.
It is easier than that.
Edit your /var/lib/portage/world
Remove anything kde-related you're not explicitly interested in, such
as kde-meta
Add anything you are explicitly interested in, such as kwooty or kwrite
Add kde
would merge, in order:
Calculating dependencies ...done!
[ebuild R ] app-portage/gentoolkit-0.2.0
#
# ls -ld /var/db/pkg/kde-base/kde*
drwxr-xr-x 2 root root 912 Sep 28 14:24 /var/db/pkg/kde-base/kde-env-3-r4
drwxr-xr-x 2 root root 912 Sep 26 21:56 /var/db/pkg/kde-base/kde-meta-3.4.1
drwxr-xr-x
1511: Called source
'/var/db/pkg/kde-base/libksirtet-3.4.3/libksirtet-3.4.3.ebuild'
libksirtet-3.4.3.ebuild, line 7: Called inherit 'kde-meta'
ebuild.sh, line 1256: Called qa_source '/usr/portage/eclass/kde-meta.eclass'
ebuild.sh, line 28: Called source '/usr/portage/eclass/kde
7.12.3 (net-nds/openldap)
--->8
$ equery d 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
On 2/14/06, b.n. [EMAIL PROTECTED] wrote:
2)Does kde 3.5 pulls in a lot of ~x86 dependecies?
You can determine this yourself:
ACCEPT_KEYWORDS=~x86 emerge -pv kde-base/kdebase-meta
3)What are current known bugs/instabilities/issues/what of KDE 3.5
packages I should be aware of? I don't use
:
Okay, I know the problem. The command you ran should actually return
nothing since you don't have any packages named kde installed. (It's a
bug that kde-env and kde-meta get returned)
Anyhow, the command you probably want to use is 'equery l kde.*' That
tells equery to return the list of all
On 12/21/11 02:11, Walter Dnes wrote:
On Tue, Dec 20, 2011 at 11:54:38PM -0700, Joseph wrote
I have a problem getting rid of KDE (those meta package might be
easy to install/upgrade but getting rid of them is not easy).
When I run emerge -uDNav world I get:
=x11-libs/qt-qt3support-4.7.2 kde
Michael Sullivan wrote:
What's a meta-flamewar???
A flamewar about flamewars.
m.
--
gentoo-user@gentoo.org mailing list
Hi!
kde.org lists kdewebdev-4.1.2 among other downloads. But there is kde-
base/kdewebdev-meta-3.5.10 in portage tree only. Does anybody know why the
package is deferred?
On Wednesday 11 Dec 2013 16:52:49 Peter Humphrey wrote:
On Wednesday 11 Dec 2013 18:39:59 Alan McKinnon wrote:
$ equery depends print-manager
* These packages depend on print-manager:
kde-base/kdeutils-meta-4.11.4 (cups ?
=kde-base/print-manager-4.11.4:4[aqua=])
Set USE=-cups
, but
note their names in case you want to put them back later
- emerge kde-meta (or if you prefer to get a smaller set instead of all of kde
follow the handbook and emerge just the -meta packages you want)
Long version:
The traditional kde packages in portage (from long long ago) mirrored
/qwebview'
* environment, line 602: Called die
* The specific snippet of code:
* emake || die emake failed;
* The die message:
* emake failed
The Gcc isi686-pc-linux-gnu-4.3.3 *
The list of emerge -pv kde-meta is this
These are the packages that would be merged
machine.
Probably cause I'm in the midst of upgrading kde via
-uD world and having a rough time of it ;(
It's installed by kdebase-startkde
I you use the -meta kde packages, get it by emerging kdebase-meta (I
can't think of a reason why anyone wouldn't want all of kdebase so
there's no need
, then the
current approach isn't so fine anymore.
Do as previously suggested and use individual meta packages instead of
the all-encompassing kde-meta,
I think, I'm doing that. And in doing that, I came to the point,
that nothing depends on kde-i18n.
I did a
find /usr/portage -name *ebuild
not compiling kde-meta either, but I've got bit more than once
with missing stuff I later needed.
When did I say meta...
I was differentiating what you did say `kdebase' with the full blown
kde-meta and noting I was somewhere in the middle with an
emerge -v kde.
I just don't find it all
Alan McKinnon [EMAIL PROTECTED] wrote:
On Friday 15 June 2007, Alexander Skwar wrote:
Sorry for not being clearer. I meant USE flags in the -meta ebuilds, to
disable undesired apps like kppp. Sort of like:
DEPEND=
kde-base/this-app
!nokppp? ( kde-base/kppp )
kde-base/that-app
-meta-3.5. But you have to remove it before
installing kde-meta-3.4. Monolithic and split packages block each other only
within the same slot.
Thanks. I know, but this is on a space constrained laptop. Removing
3.4 altogether should do me nicely.
In general it helps to tell us what you want
Hello,
Some time ago, I upgraded several systems I manage.
First was the (painful) upgrade of kde-monolith
to kde-meta. [1]
Then the easier of the two xorg 6.8 to xorg 7.0. [2]
I have kept these pacakges masked for a while on other systems,
some of which I only get possession of sporadically
Dale
>>
>> :-) :-)
> Good call Dale, here's what I found:
>
> app-accessibility/speech-dispatcher is required by dev-qt/qtspeech,
>
> which is required by kde-apps/kdepim-runtime and kde-apps/kpimtextedit,
> neither of which have a USE flag to stop speech-dispatcher kick
; 381 KiB
> [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)
> [ebuild NS] kde-apps/kdemultimedia-me
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/kdemultimedia-meta-15.12.3:5::gentoo
[4.14.3:4::gentoo] USE="ffmpeg" 0 KiB
[uninstall
snip-
blocks^[[39;49;00m b^[[39;49;00m ]
kde-base/kdeartwork-meta:4.6[-kdeprefix]^[[39;49;00m
(kde-base/kdeartwork-meta:4.6[-kdeprefix] $
[ebuild^[[39;49;00m NS^[[39;49;00m ] kde-base/kde-meta-4.6.2^[[39;49;00m
[4.4.5]^[[39;49;00m USE=nls^[[39;49;00m semantic-desktop^[[3
by kde-base/kdenetwork-meta-3.5.10 [installed])
(dependency required by kde-base/kde-meta-3.5.10 [installed])
(dependency required by @world [argument])
r...@smoker / #
As I understand this, kde-meta:3.5 is in world, which it is, kde-meta
pulls in kdenetwork-meta which pulls in kopete. It seems
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, in order:
Calculating dependencies | *
* ERROR: kde
'.
KWallet only depends on kdeutils-meta. If you want to get rid of it unmerge
kdeutils-meta and add the packages pulled in by kdeutils-meta to the world
file (/var/lib/portage/world). You can find the names of these packages in the
kdeutils-meta ebuild:
RDEPEND=
$(deprange $PV $MAXKDEVER kde-base
ones, but with -meta
appended (kdepim-meta). Those usually install the same applications
than
monolithic ebuilds, but as split ebuilds.
So, when you install kde, you get a complete KDE from monolithic
ebuilds
and
when you install kde-meta, you get a complete KDE from split ebuilds
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
Your quoting style is terrible...!
On Saturday 24 June 2006 17:25, James wrote:
Unmerge what you don't need or remerge (after emerging kde 3.5) what
you still need. When you are done with that the above command should
give no output and any files still in /usr/kde/3.2 - 3.4 can
. The contents of /etc/portage/*
is seldom useful here as blockers almost always mean you have specified
two things that cannot co-exist.
In your case, you have run into monolithic and -meta kde ebuilds. Guess
what - you already have the kompare binaries, despite the fact that
kde-base/kompare
would like to use my /etc/portage/package.use file (as is the proper
way right), so what package(s) entry should I put in there to USE
'wifi'?
If I try to emerge -Dav kde-base/kdenetwork-meta I get all kinds of
packages that are blocked by =kde-base/kdenetwork-3.4*
You want kdenetwork
On Saturday 09 Jul 2016 23:22:49 I wrote:
> On Sunday 10 Jul 2016 04:08:36 Michael Palimaka wrote:
--->8
> > This change is correct - we're in the process of cleaning up some old
> > ebuilds at the moment.
> >
> > In this case kde-apps/kdebase-runtime-meta:5 doesn'
oment.
> > >
> > > In this case kde-apps/kdebase-runtime-meta:5 doesn't imply anything
> > > KF5-based - it has just been ported to use a newer eclass. It still
> > > just pulls in the old KDE4-based kde-runtime packages.
>
> I don't think that's entirely
/kdebase-meta-4.1.4', 'merge')
kde-base/phonon-xine:4.1[xcb] required by ('ebuild', '/',
'kde-base/dragonplayer-4.1.4', 'merge')
For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
http
with KDE 3.4, which makes me wonder why and older version is blocking things. emerge kde-meta and see what kind of trouble it gives you.
On Thursday 06 October 2005 04:46, Wes Gray wrote:
My 3-year old gentoo system has decided to be a big headache. My
troubles started when I upgraded to kde 3.4. The kde taskbar apps
wouldn't start. I tried unmerging kde-base and emerging kdebase-meta
to see if it was related to the kde
are
only intended to make installing kde easier, which they do, but it
doesn't make handle uninstalling or reinstalling a split ebuild very
easy at all. Like, if I had kde 3.4 installed and upgraded to 3.5 and
no longer need 3.4, I can't just do 'emerge -C kde-meta-3.4', or
something similar
actually only want individual packages on my system, so I didn't install
it. However, something is now trying to pull it in.
eix -e of kdebase and kde shows that neither is installed (not the
monolithic nor the meta package).
equery depends kdebase lists:
app-cdr/k3b-0.12.4a
kde-base/kdm-3.4.1
kde
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
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. That's
how I do it.
Paul
/superkaramba-3.5.0 +arts -debug
-kdeenablefinal -kdexdeltas -xinerama 2,888 kB
You cannot mix split and monolithic ebuild for the same part of KDE.
Superkaramba is in kdeutils, so you cannot also merge it separately.
Either remove suprerkaramba or emerge kdeutils-meta instead of kdeutils
On 4/10/06, Daniel [EMAIL PROTECTED] wrote:
Actually, I tried using --tree --verbose earlier. Strangely enough, it looks
like KPDF is requiring this. I alread have Konqueror installed:
Ok. I am getting lost in the maze of the kde-functions and kde-meta
eclasses, but I think this is because
On Sat, 24 Jun 2006 18:28:39 +0200, Bo Ørsted Andresen wrote:
You seem to have been more confused than enlightened by the tricks I
posted. If you want to nuke kde completely you should just do:
# cd /var/db/pkg emerge -Cva kde-base/*
You should also rm -fr /usr/kde or rm -fr /usr/kde/3.[0
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 files from the overlay
My laptop normally runs gnome but T want to demo some other desktops
tomorrow and kde is giving me problems - kde-meta 4.4.5 is installed. I
think last time I did this it was kde-3.5 but that almost two years ago
now and the same method isnt working for 4.4.5. I have a different user
setup
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 sweep?
grep kde /var/lib/portage/world
and eyeball the output. There should only be -meta packages
On Friday 18 January 2008, Bo Ørsted Andresen wrote:
On Thursday 17 January 2008 17:06:28 Alan McKinnon wrote:
Roll on KDE4 when this monolithic nonsense will go away and there
will only be -meta ebuilds.
Actually it was decided to keep monolithics in KDE 4.0.0. Splits are
now the default
is required to complete your
request:
- kde-base/kdm-3.5.7 (masked by: ~x86 keyword)
For more information, see MASKED PACKAGES section in the emerge man page
or refer to the Gentoo Handbook.
(dependency required by kde-base/kdebase-meta-3.5.7 [ebuild])
I synced a couple of times
2016-04-09 5:12 GMT-05:00 Mick <michaelkintz...@gmail.com>:
> I noticed to day that Plasma 5 is now stable, which means I will soon have
> to
> deal with it. I run a number of boxen with Gentoo on them. Some of them
> do
> not run a full KDE desktop, only selected KD
I've just updated all my installed pkgs ( c 112 ) for KDE
(apps frameworks plasma), except for 'plasma-meta',
which raises an error :
Error: The above package list contains packages which cannot be
installed at the same time on the same system.
(gnome-base/gnome-common-3.18.0-r1:3/3
On Friday 13 January 2006 22:59, John Jolet wrote:
emerge Xorg? or emerge kde-meta
Xorg and KDE both are emerged and I am using this kernel on already existing
system. If you are saying that I should reemerge them, then wouldn't I bork
my already working 32bit system?
--
Regards,
Abhay
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
:-)
--
Neil Bothwick
The trouble with the world is that everybody in it is three drinks behind.
signature.asc
not a
dependency?
Hum, that is bizarre. I just tried emerge -pvt kde-meta, and it shows
that kde-meta depends on kdebase-meta depends on kdebase-startkde
(all version 3.5.9)
Checking all the ebuilds currently in the tree (versions 3.5.9,
3.5.10, 4.1.2 and 4.1.3), shows that all versions
On Sun, 23 Apr 2006 02:46:18 +0530, Abhay Kedia wrote:
Or you could simply do the sensible thing and use KDE ;-)
Ouch!!! I hope you have your flame suit on!
It's installed as part of kde-meta ;-)
--
Neil Bothwick
...And it's 'WORF', not 'Woof'. * Worf
signature.asc
Description: PGP
On Sun, 11 Jun 2006 16:12:48 -0700, Kevin O'Gorman wrote:
I first guess is to unmerge everything KDE, but even then, I'm not quite
sure
Not everything KDE, leave arts and any other dependencies
what I should emerge in its place. kde-meta? And what will my system
be capable
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 those?
--
Rgds
Peter
Hi,
is there a command which shows all dependencies of a package?
Unfortunately, qdepends doesn't do the job, e.g.
qdepends kde-base/kde-meta shows no dependencies at all while there are
more than 200 of them.
Many thanks for a hint,
Helmut.
Peter Ruskin wrote:
With big hard discs cheap and with ADSL
connection, the advantages of the meta packages are diminished.
If I understand your meaning correctly, not everyone can get broadband.
I'm on dial-up and it is all that is available here where I live. DSL
may be here soon
On 2007-06-15, Dale wrote:
Peter Ruskin wrote:
With big hard discs cheap and with ADSL
connection, the advantages of the meta packages are diminished.
If I understand your meaning correctly, not everyone can get broadband.
I'm on dial-up and it is all that is available here where I live
Wes Gray wrote:
# grep kde /var/lib/portage/world | sort
kde-base/arts
kde-base/kde-env
kde-base/kde-meta
kde-base/kdebase-meta
kde-base/kdelibs
kde-base/konqueror
Hmm, if I'm not mistaken, if you've emerged kde-meta, none of the
other kde things should be in your world file. You've
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 this hacked-together list instead:
[EMAIL PROTECTED] /var/portage/kde-base $ cd /var/portage/kde-base/
[EMAIL PROTECTED] /var/portage
-3.5.10-r2 but some
are in use with were built with kde-base/kdelibs-3.5.9-r4, e.g.
app-office/kformula When I try to re-emerge app-office/kformula separately
it fails
with some linker errors.
So, how can I cut my Gordian knot? (except re-emerging the whole
kde-meta:3.5)
Many thanks for a hint
-2.2_rc62 is unable to cope with that.
Remove ALL version-specific information for kde entries from world.
There are no specific version of kde in world
Don't mix and match -meta packages and sets.
What do you mean by that? I don't think I have any kde-sets here
# emerge --list-sets
downgrade
On Tue, Dec 20, 2011 at 11:54:38PM -0700, Joseph wrote
I have a problem getting rid of KDE (those meta package might be
easy to install/upgrade but getting rid of them is not easy).
When I run emerge -uDNav world I get:
=x11-libs/qt-qt3support-4.7.2 kde
=x11-libs/qt-webkit-4.7.2 kde
My
e it as one.
The thing with KDE is that it is designed as an integrated environment
and intended to be used as such. So trying to install an individual
program is bound to bring in the backend support stuff.
Switching to a non-KDE profile, unmerging everything KDE with
emerge -cav $(qfile -IC kde
On Wednesday 30 May 2007 21:16:18 Mat Harris wrote:
Don't use --nodeps. That would just make a mess out of [your] system. If
you've installed split kde (kde-meta) then why are you trying to install
monolithic kde packages? I.e. why are you trying to install kdebase
rather than kdebase-meta
On Sun, 01 Feb 2009 12:38:22 +0100 (CET), Helmut Jarausch wrote:
since kde-4.2 seems be to unblocked now, I'd like to try it.
But there are 408 (!) blocked packages.
emerge --unmerge kde-meta
didn't do anything.
So, what's a feasible way to upgrade?
Use automunmask, as already mentioned
Am Sonntag, 5. Oktober 2008 10:10:33 schrieb [EMAIL PROTECTED]:
solfire:/rootemerge kde-meta
Calculating dependencies -!!! Digest verification failed:
!!! /usr/portage/kde-base/kdebase-startkde/kdebase-startkde-4.1.2-r1.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 4061
.
Yea, I have that one. I think I did kde-meta for my install and I think
it got ALL the KDE stuff. O_O
Dale
:-)
--
gentoo-user@gentoo.org mailing list
301 - 400 of 1441 matches
Mail list logo
