1
0
Fork 0
This repository has been archived on 2021-01-06. You can view files and clone it, but cannot push or open issues or pull requests.
dennogumi.org-archive/_posts/2014-04-24-kdecurrent-and-4-13-packages-for-opensuse.markdown

82 lines
4.1 KiB
Markdown
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
author: einar
comments: true
date: 2014-04-24 20:35:47+00:00
layout: page
slug: kdecurrent-and-4-13-packages-for-opensuse
title: KDE:Current and 4.13 packages for openSUSE
wordpress_id: 1302
categories:
- KDE
- Linux
- openSUSE
tags:
- featured
- KDE
- openSUSE
---
_This is a guest post by Raymond "tittiatcoke" Wooninck, with contributions from myself and Hrvoje "shumski" Senjan_
In the next hours the [KDE:Current]({{ site.url }}/2014/03/being-current/) repository will publish t[he latest release from KDE (4.13)](http://kde.org/announcements/4.13). As that this release comes with a big change ([the new semantic search](http://dot.kde.org/2014/02/24/kdes-next-generation-semantic-search)), we would like some simple steps in order to perform the right upgrade.
### Before the upgrade
In order to migrate data automatically from the Nepomuk store to the new format, you will need Nepomuk up and running, and just for the time needed for the migration. Ensure that Nepomuk is running before the update (in System Settings > Desktop Search). This is only necessary in case Nepomuk is in use on the system.
### The upgrade itself
*  If you are already using KDE:Current then the upgrade should be a simple _zypper up_ or upgrade packages through YaST Software Management.
*  If you are not yet using KDE:Current, then please follow the instructions [on the wiki](https://en.opensuse.org/KDE_repositories#Current_KDE_SC_release)  on how to add the necessary repositories. After adding them, a _zypper dup_ is required to ensure that all the KDE packages are coming from KDE:Current.
Please do not remove nepomuk, as that otherwise the migration to baloo will fail. Also after the upgrade please make sure that the **baloo-file** package is installed (it is required for indexing). After this check, log off and back on. The Nepomuk migrator will then run and move all the data that can be migrated to the new system. It will also turn off Nepomuk at the end of the migration.
At this moment it would be safe to remove the nepomuk related packages like nepomuk-core, libnepomukwidgets, soprano*, strigi, virtuoso and shared-desktop-ontologies. There are only a few packages left that are stillrequiring the Nepomuk framework (like bangarang, kweshtunotes, etc).
### Using the new search system
Unlike the 'include folders to be indexed' used with Nepomuk, the new search backend prefers to index everything and exclude unwanted folders explicitly. With the standard setup,  all files and directories below the home-directory will be indexed. All other
filesystems are indicated as omitted.
This can be changed by deleting the respective entries in System Settings. To turn indexing off completely, add your home directory to the excluded folder list (bear in mind that this will prevent search from working). To remove the components completely, remove the **baloo-file** package. The package **baloo-pim** (only present when kdepim is installed) can be removed if no search capabilities are required for KMail.
Aside from Dolphin, the only search UI  available is the package called
**milou**. Milou can be placed in the panel for easy access and its usage is quite simple. The search term is indicated and search results are shown for files, emails, and so on.  You can pick which categories to use in the settings.  At the moment you should _not_ put Milou in the system tray, because it will cause Plasma to crash at login.
Tags in the files are now stored using extended attributes (xattrs) instead that in the database.
### Known issues
* The initial indexing can be heavy on I/O especially if there are large text files: either wait till the indexing is complete (this step is done only once), or exclude the folder containing such files.
* Some data will be lost during the migration: in particular, emails will have to be re-indexed, and file<->activity associations, if used, will not be preserved.
### Reporting problems
As usual, use [Novell's Bugzilla](http://bugzilla.novell.com) if you find issues pertaining to the specific packaging used in openSUSE: otherwise, report bugs [directly to KDE](https://bugs.kde.org).