| 1 |
Robert Walter posted <200605040316.34157.ro-wa@×××.at>, excerpted below, |
| 2 |
on Thu, 04 May 2006 03:16:34 +0200: |
| 3 |
|
| 4 |
> hi |
| 5 |
> (posting to gentoo-user and gentoo-amd64) |
| 6 |
> |
| 7 |
> with krename version 3.0.9 to 3.0.11, the 2 servicemenu files |
| 8 |
> (krename_dir.desktop, krenameservicemenu.desktop) changed the location. |
| 9 |
> that's why the konqueror action "rename with krename" when right-clicking |
| 10 |
> on a file or directory disappeared. a simple mv solved the problem |
| 11 |
> $ mv /usr/share/services/krename* |
| 12 |
> /usr/kde/3.4/share/apps/konqueror/servicemenus/ |
| 13 |
> |
| 14 |
> my questions now. |
| 15 |
> should that be reported as a bug? |
| 16 |
> because the problem is in the source tar not in the ebuild, it's rather a |
| 17 |
> kde than a gentoo problem, right? what would you do? |
| 18 |
> |
| 19 |
> best regards. robert |
| 20 |
> |
| 21 |
> ps. i run kde 3.4.3 |
| 22 |
|
| 23 |
The problem seems to have been resolved with the latest, KDE-3.5.2 |
| 24 |
(krename-3.0.11), or at least I have the actions, here. |
| 25 |
|
| 26 |
Both those files are located in /usr/share/services/ and reported by |
| 27 |
equery as belonging to krename. A quick verification check reveals no |
| 28 |
krename* files in /usr/kde/3.5/share/apps/konqueror/servicemenus/. It |
| 29 |
appears KDE now looks for and honors files in either location. |
| 30 |
(konsolehere.desktop is in the kde/3.5 location and the action appears, |
| 31 |
krename_dir.desktop is in the generic location and the action appears, so |
| 32 |
it's seeing and using both.) |
| 33 |
|
| 34 |
In any case, it'd be a Gentoo bug, not upstream, because the tarball |
| 35 |
places it in the standard location as it should. The /usr/kde/<ver> |
| 36 |
location is Gentoo specific, due to the fact that Gentoo slots KDE, so |
| 37 |
any bugs related to that path as contrasted with the upstream/standard |
| 38 |
path are normally going to be Gentoo bugs. |
| 39 |
|
| 40 |
Here we have kde-misc/krename, not kde-base/krename. As such, it's not |
| 41 |
part of the main KDE release, but a separate package. Core KDE is slotted |
| 42 |
by Gentoo, so you can have kde-3.4 and kde-3.5 installed in parallel, if |
| 43 |
desired. Anything in kde-misc, as opposed to kde-base, won't be slotted, |
| 44 |
however. What that means is that the core stuff, that is, the stuff in |
| 45 |
kde-base, will be merged to the slotted location, /usr/kde/<ver>/, while |
| 46 |
kde-misc packages and other KDE packages not in kde-base will merge to |
| 47 |
/usr/. |
| 48 |
|
| 49 |
You wouldn't want non-slotted packages in /usr/kde/<ver> anyway, because |
| 50 |
that would break stuff when the slotted packages were upgraded and the old |
| 51 |
slotted packages eventually unmerged/pruned. You'd be left with the old |
| 52 |
slot dirs still around, after everything in that slot had been unmerged, |
| 53 |
because unslotted packages had wrongly been merged into the slotted |
| 54 |
location. |
| 55 |
|
| 56 |
Thus, while moving the file might work, it would be preferable to symlink |
| 57 |
it, if necessary, so the file stays in its unslotted location. It'll |
| 58 |
probably save you having to remerge krename later, when you /do/ upgrade |
| 59 |
to kde-3.5.*. The symlink will still cause the old 3.4 slotted dir it |
| 60 |
exists in to remain behind (as not empty) when the last of the 3.4 |
| 61 |
packages is pruned/unmerged, but that's not quite as serious as it |
| 62 |
won't cause krename to be broken with 3.5 until you fix it, and it should |
| 63 |
be as easy to rectify manually as creating the symlink was in the first |
| 64 |
place. |
| 65 |
|
| 66 |
-- |
| 67 |
Duncan - List replies preferred. No HTML msgs. |
| 68 |
"Every nonfree program has a lord, a master -- |
| 69 |
and if you use the program, he is your master." Richard Stallman in |
| 70 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
| 71 |
|
| 72 |
|
| 73 |
-- |
| 74 |
gentoo-amd64@g.o mailing list |
Archives