|General||Source||Linux Packages (.rpm and .deb)||Windows||Known bugs||Mac ports||Updated Filters||Translations|
The current version is 1.21.7. Release notes.
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.
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 release file), there is probably no necessity to upgrade anyway.
Current release distribution: 1.21.7:
As with any .0 release, don't use this is you absolutely don't want to run into trouble:
Ubuntu Unity Lens and Scope
You will probably get these from the PPA, but here are the source files. These are not included in the main tar file any more. For recoll 1.19, 1.20 and 1.21 installations (choose on the Ubuntu version, not the Recoll one):
recoll-lens-184.108.40.20643.tar.gz (Recoll 0.19 or 0.20, Ubuntu up to 13.04 Raring)For Recoll 1.18: recoll-lens-220.127.116.1197.tar.gz
unity-scope-recoll-18.104.22.168.tar.gz (Recoll 0.19 and later, Ubuntu 13.10 and later).
For Recoll 1.17: recoll-lens-22.214.171.12497.tar.gz
Prerequisites for building from source:
- C++ compiler. Its absence sometimes manifests itself by strange messages about iconv_open (fixed after 1.13.04).
Xapian core development libraries. Most Linux distributions carry them in their package repository. Or you will find source and binary packages on the Xapian download page.
Recoll should still work with Xapian 1.0, but it is highly recommended to use a Xapian 1.2 version.
Note on building Xapian for older CPUs: The build configurations for Xapian releases 1.0.21 and 1.2.1 or newer enable the use of SSE2 floating point instructions. These instructions are not available in CPUs older than Intel Pentium 4 or AMD Athlon 64. When building for such a CPU, you need to add the --disable-sse flag to the Xapian library configure command. If this is not done, the problem signals itself by "Illegal instruction" crashes (SIGILL) in recollindex and recoll.
- X11 development files.
- zlib development files.
Qt development files: Qt 4.4 or newer. The Recoll GUI will not build with Qt releases older than 4.4.
Qt webkit development: Qt WebKit is quite often distributed apart from the main Qt lib. It is possible to configure Recoll not to use Qt WebKit (see configure --help).
- Python development package: you can avoid needing this by configuring with --disable-python-module.
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.
Instructions for building
Normally, it's just ./configure; make; make install. If a bit more detail is needed, there is some in the manual.
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 some pointers to find newer packages for some distributions. In most cases, you will just need to use an alternate repository.
I sometimes build binary packages when no appropriate repository exists. Any binary package directly linked from 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.
The Debian Recoll packages are usually fairly up to date, just use the appropriate Debian repository.
Except they're not at the moment (2015-10).... So I am maintaining a repository for packages built for Debian Wheezy, and Jessie. This currently has recoll 1.21.x (the standard repos have 1.17...) To add the repository to your sources:
The public part of the key used to sign the repositories can be downloaded and installed as follows:
- Create and edit
and add the following lines:
for wheezy (debian 7.x):
deb http://www.lesbonscomptes.com/recoll/debian/ wheezy main deb-src http://www.lesbonscomptes.com/recoll/debian/ wheezy mainfor jessie (debian 8.x):
deb http://www.lesbonscomptes.com/recoll/debian/ jessie main deb-src http://www.lesbonscomptes.com/recoll/debian/ jessie main
sudo apt-get update sudo apt-get install recoll [python-recoll python3-recoll]
If you prefer to manually install the packages, they are here:
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
The packages in the PPA now have a separate package for the Python extension, like the standard ones, so there should be no more conflict issues while switching from the PPA to the normal repositories and back.
The Ubuntu PPA works perfectly for Mint 13 (and probably other releases too). Just follow the instructions for Ubuntu.
You'll need to install the Xapian, Qt, Qt-Webkit and zlib development packages if you want use the source rpms.
Recoll is present in the standard Fedora package repositories starting from F-12. Recoll packages in Fedora are usually fairly up to date. Please get in touch if you have a need for a Recoll package for Fedora.
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.
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:
- Install MacPorts.
- Type "sudo port install recoll"
Recoll is then available from the command line and as an icon in the usual MacPorts applications place.
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.
Most of the translations for 1.21 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
recoll_xx.ts is a blank Recoll 1.21 message file, handy to work on a new translation. You can also list the directory to see all the translation files (same as those in the 1.20 source branch on Bitbucket).
Updated 1.20/21 translations that became available after the release:
Note that, if you are running an older release, you may find updated messages by looking inside the appropriate maintenance branch on bitbucket.