Recoll downloads

Source Packages (.rpm and .deb) Known bugs Mac ports Filters Translations

General information

The current version is 1.17.4. Release notes.

The download page for Recoll 1.16 is still available.

Recoll Installation / building manual.

The indexing filters used for some document types may need external packages not installed on your system by default, and not installed automatically with Recoll: take a look at the list and decide what you need to install. Also new or updated filters sometimes become available after a release. As a rule, all filters are compatible with all Recoll versions. Any compatibility problem will be explicitely mentionned.

The Recoll term explorer tool in phonetic mode (marginally useful and optional) uses the aspell package, version 0.60 (utf-8 support) or newer.

If you find problems with this page, the package or its installation, please report them.

What do the release numbers mean?

The Recoll releases are numbered X.Y.Z. The X would only change for really major modifications like a big change in the index format, and possibly won't ever reach 2.

Y is for functional modifications. These may bring bugs, so if you don't need the new features, you may want to wait a little, and especially skip the first release (X.Y.0), at least for a few weeks.

Z changes for bug fixes only, and moving from X.Y.Z to X.Y.Z+u should in general involve little risk of regression. But, any change can bring problems, if you are not affected by the corrected bugs (check the changes file), there is probably no necessity to upgrade anyway.

Source

Current release distribution: 1.17.3:

recoll-1.17.4.tar.gz.

Prerequisites for building from source:

Source repository:

The Recoll source repository is hosted on bitbucket.org. The trunk is usually a bit on the bleeding edge, but there is always a maintenance branch for the current production version.

Older recoll releases:

1.17.3. 1.17.2. 1.17.1. 1.16.2. 1.15.9. 1.14.4. 1.13.04. 1.12.4. 1.11.4. 1.10.6. 1.9.0. 1.8.2. 1.7.6. 1.6.3. 1.5.11. 1.4.3. 1.3.3. 1.2.3. 1.1.0. 1.0.16.

Packages

Packages or ports for Recoll are available in the standard repositories for many distributions.

However they are often a bit older or built with older Xapian releases. Here follow a number of updated packages and instructions for a number of distributions.

All binary packages on this page need a Qt 4 (4.4 at least) runtime environment. To make things easier, on systems where Xapian is not available from the standard package repositories, the Recoll package will have a static link to Xapian so that you do not need to build/install it separately.

Debian

The Debian Recoll packages are usually fairly up to date (at least in testing), just use the appropriate Debian repository.

Ubuntu

There are Personal Package Archives on launchpad.net for Recoll, kio-recoll and recoll-lens. These were built from the latest versions, for a set of Ubuntu series. starting at Lucid. The installation is very simple:


          sudo add-apt-repository ppa:recoll-backports/recoll-1.15-on
          sudo apt-get update
          sudo apt-get install recoll
          

Linux Mint

The Ubuntu PPA works perfectly for Mint 13 (and probably other releases too). Just follow the instructions for Ubuntu.

RPMS

Some Fedora and Mandriva packages unfortunately think that they depend on exiftool (which is needed by the little used jpeg info filter), due to excessive rpmbuild cleverness.
You'll need to install the Xapian, Qt, and zlib development packages if you want use the source rpms.

Fedora

Recoll is present in the standard Fedora package repositories starting from F-12. The new versions are tracked quite closely, so I don't build the rpms any more (email me if you need one).

OpenSUSE

Recoll is in the KDE:Extra repository You just need to add the repository to your software sources (Yast2->software->Software repositories).
Repository list (supported Suse versions). After adding the appropriate repository to your software sources, you will be able to install recoll and kio_recoll from the software management interface. The Xapian dependancy will also be satisfied from the build service repository. Some of the older repositories do not build antiword, just tell the software manager to "break" recoll by installing anyway, and get antiword somewhere else.

Mandriva

Mandriva linux 2011 using Qt 4 and the Xapian version from the Mandriva repository.: recoll-1.17.2-1-mdv2011.0.i586.rpm, recoll-debug-1.17.2-1-mdv2011.0.i586.rpm.
Source: recoll-1.17.2-1.src.rpm

Ports

Mac port

It seems that Recoll will sometimes find data that Spotlight misses (especially inside pdfs apparently, which is probably more to the credit of poppler than recoll itself).

Recoll is in MacPorts and really easy to install:

  1. Install MacPorts.
  2. Type "sudo port install recoll"

Recoll is then available from the command line and as an icon in the usual MacPorts applications place.

Building on Solaris

I did not test building the GUI on Solaris for this version. You will need at least Qt 4.4. The old hints in the previous page may still be valid.

Someone did test the indexer and Python module build, they do work, with a few minor glitches. Be sure to use GNU make and install.

Translations

Most of the translations for 1.17 are incomplete The source translation files are included in the source release. If your language has some english messages left and you want to take a shot at fixing the problem, you can send the results to me and earn my gratefulness (and your less multilingual compatriot's)...

You can use the .ts file to alter the translations if you wish (use Qt's linguist tool to edit the source file, then lrelease to produce the .qm file.). The .qm file should be copied to /usr/[local/]share/recoll/translations

recoll_xx.ts is a blank Recoll 1.17 message file, handy to work on a new translation.

Updated 1.17 translations that became available after the release:

A Greek translation for 1.17, thanks to Dimitrios recoll_el.ts recoll_el.qm

Note that, if you are running an older release, you may find updated messages by looking inside the appropriate maintenance branch on bitbucket.