Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 257221
Alias:
Product:
Component:
Status: NEW
Resolution:
Assigned To: Gentoo KDE team <kde@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Matěj Laitl <strohel@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 257221 depends on: Show dependency tree
Bug 257221 blocks: 239356
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.








View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2009-02-01 14:36 0000
Hi,
I've noticed that update-mime-database is not run for
/usr/kde/4.{1,2}/share/mime, which is the mime dir when kde is built with
kdeprefix use-flag set. The ebuild calls fdo-mime_mime_database_update from
fdo-mime.eclass, but this command hardcodes mime path to /usr/share/mime.

One symptom of this problem is that java applets do not work in konqueror until
you run update-mime-database /usr/kde/4.{1,2}/share/mime - see [1]

Regards, Matěj

[1] https://bugs.kde.org/show_bug.cgi?id=161825

------- Comment #1 From Tomáš Chvátal 2009-02-01 15:03:26 0000 -------
How about symlink between /usr/kde/4.X/share/mime and /usr/share/mime.
That should work right?

------- Comment #2 From Matěj Laitl 2009-02-01 15:12:53 0000 -------
(In reply to comment #1)
> How about symlink between /usr/kde/4.X/share/mime and /usr/share/mime.
> That should work right?
> 

I don't think so - as kde 4.1 and 4.2 install slightly different mime packages
here, potentially interfering with each other. So symlinking before
installation is not really a solution. I don't think the problem is that the
mimo info is in separate dir, as it's just some kde-specific stuff.

My proposed solution is to extend fdo-mime eclass to allow updating custom
directories.

------- Comment #3 From Gilles Dartiguelongue 2009-11-01 00:20:23 0000 -------
In that case making it use XDG_DATA_DIRS as a reference would probably be a
good idea.

------- Comment #4 From Romain Perier 2009-11-01 18:37:28 0000 -------
scarab I agree with Matěj... and if a directory like that exists on upstream
(I meant if upstream devs want to install mime in this dir) I suppose there is
a good reason... :)

idea for XDG_DATA_DIRS looks good, for example :

XDG_DATA_DIRS=${XDG_DATA_DIRS:-${ROOT}/usr/share/mime}

fdo-mime_mime_database_update() {
        if [ -x "/usr/bin/update-mime-database" ]
        then
                einfo "Updating shared mime info database ..."
                "/usr/bin/update-mime-database" "${XDG_DATA_DIRS}"
        fi
}

something like that...


Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug