SEO

I'm seeing output of this type (see below) more often and prior ebuilds are
being removed but not replaced with newer. For instance, kpackage was
available until recently.

localhost / # which kpackage
which: no kpackage in (/sbin:/bin:/usr/sbin:/usr/bin)

localhost / # emerge -p kpackage

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[blocks B ] =kde-base/kdeadmin-3.4* (is blocking
kde-base/kpackage-3.4.3)
[ebuild N ] kde-base/kpackage-3.4.3

I could unmerge kdeadmin-3.4* and do kpackage and whatever else was removed.
But the larger concern is ultimately will "3.4*" cause larger problems? The
"3.4*" is the result of doing "emerge kde" months ago (Oct.,2005) after
replacing a failing harddrive and rebuilding the system.

Your time is appreciated !
--
BlackTopBum
You don't skateboard?
What worthwhile thing are you doing !?

BlackTopBum wrote:

> Calculating dependencies ...done!
> [blocks B ] =kde-base/kdeadmin-3.4* (is blocking
> kde-base/kpackage-3.4.3)
> [ebuild N ] kde-base/kpackage-3.4.3
>
> I could unmerge kdeadmin-3.4* and do kpackage and whatever else was removed.
> But the larger concern is ultimately will "3.4*" cause larger problems? The
> "3.4*" is the result of doing "emerge kde" months ago (Oct.,2005) after
> replacing a failing harddrive and rebuilding the system.

kde-base/kpackage is part of the modular kde build tree called kde-meta, you
can't mix kde-meta packages with kde packages and I would guess that the kde
package kde-base/kdeadmin already does supply you with the kpacakge program,
take a look in your /usr/kde/3.4/bin


//Aho

J.O. Aho said something like a ...

> take a look in your /usr/kde/3.4/bin

WT-? It's there. It's not in the Menu or path, nor for root, but it's there.
Go figure. Thanks !
--
BlackTopBum
You don't skateboard?
What worthwhile thing are you doing !?

BlackTopBum wrote:
> J.O. Aho said something like a ...
>
>> take a look in your /usr/kde/3.4/bin
>
> WT-? It's there. It's not in the Menu or path, nor for root, but it's there.
> Go figure. Thanks !

IMHO there are a lot of stuff that don't appear in the KDE menu, here was
RedHat 7.x a lot better, the GUI software was always included into KDE/Gnome
menus when installed, while in Gentoo we don't always get everything into KDE
menus, I guess the Gnome2 guys don't bother about others.


//Aho

J.O. Aho said something like a ...

> while in Gentoo we don't always get everything into KDE
> menus,

Yeah, ever try the Menu Updating Tool? Rarely has it anything new listed
even though I _know_ there are several apps available - of which I had, and
still do, execute from the command line.
--
BlackTopBum
You don't skateboard?
What worthwhile thing are you doing !?

BlackTopBum wrote:
> J.O. Aho said something like a ...
>
>> while in Gentoo we don't always get everything into KDE
>> menus,
>
> Yeah, ever try the Menu Updating Tool? Rarely has it anything new listed
> even though I _know_ there are several apps available - of which I had, and
> still do, execute from the command line.

I have been making my global menu entries manually. Other times I get doublets
of the menu entires, one for KDE and one for Gnome2, and both appears in the
KDE menu, there really is a need to do menu entries better.


//Aho

On Tue, 14 Feb 2006 03:05:47 +0100, J.O. Aho wrote:

> BlackTopBum wrote:
>> J.O. Aho said something like a ...
>>
>>> while in Gentoo we don't always get everything into KDE
>>> menus,
>>
>> Yeah, ever try the Menu Updating Tool? Rarely has it anything new listed
>> even though I _know_ there are several apps available - of which I had, and
>> still do, execute from the command line.
>
> I have been making my global menu entries manually. Other times I get doublets
> of the menu entires, one for KDE and one for Gnome2, and both appears in the
> KDE menu, there really is a need to do menu entries better.
>
>
> //Aho

Had a similar problem with kde's menu and the fix was a bit drastic but
worked quite nicely. You need to locate the .kde folder and look for kderc
file. Be careful as you don't want to screwup kmailrc or other apps such
as korganizier, you specifically want to double check the file by opening
it with nano/kwrite or other text editor. Once you've confirmed the file
is the kdeconfig file delete it, shutdown and restart kde. This will throw
you back to the kde config screen and will rebuild the entire menu
structure with all of the kde apps added and no, I don't know why kde
can't reinitialize the menu or include a comand to rebuild it with all of
the defaults but this will ensure that all of the defaults are there and
then you have to go through the aggravation of reconfiguring the entire
menu structure to your tastes once again.

The method I've decided upon for the menu is to just move things into
sub-folders as I don't care to delete them with the exception of those
items that show up in the update menu tool. I used this method just a
couple of weeks ago after doing a fresh install. Solved several menu
problems along with adding in all of my missing icons.

Test wrote:
> On Tue, 14 Feb 2006 03:05:47 +0100, J.O. Aho wrote:
>
>> BlackTopBum wrote:
>>> J.O. Aho said something like a ...
>>>
>>>> while in Gentoo we don't always get everything into KDE
>>>> menus,
>>> Yeah, ever try the Menu Updating Tool? Rarely has it anything new listed
>>> even though I _know_ there are several apps available - of which I had, and
>>> still do, execute from the command line.
>> I have been making my global menu entries manually. Other times I get doublets
>> of the menu entires, one for KDE and one for Gnome2, and both appears in the
>> KDE menu, there really is a need to do menu entries better.

> Had a similar problem with kde's menu and the fix was a bit drastic but
> worked quite nicely.
<cut a lot>
> can't reinitialize the menu or include a comand to rebuild it with all of
> the defaults but this will ensure that all of the defaults are there and
> then you have to go through the aggravation of reconfiguring the entire
> menu structure to your tastes once again.

The problem isn't default menu entries, it's all the stuff you emerge later
on, which do not create a valid *.desktop for the menu.

Other applications you emerge places a *.desktop in
/usr/kde/<version>/share/... and another in /usr/share/... which nicely gives
you two of the same menu entires in your KDE menu.


//Aho