Revision as of 11:50, 23 August 2012

Other languages:

Note

This page lists binary (installation) copies of the Calligra Suite prepared for users. You can also download its full source code.

Stable Release

Calligra 2.5 is the current stable version.

Arch Linux

Arch Linux provides Calligra packages in the [extra] repository.

Chakra Linux

Chakra Linux provides Calligra packages in the desktop repository.

The Chakra LiveDVD comes with the latest Calligra pre-installed.

Debian

Debian provides Calligra packages in its unstable repository and testing repository.

Fedora

Fedora packages for Calligra are available in the unstable repository of the KDE Packaging Project.

FreeBSD

FreeBSD features stable packages in the ports tree via editors/calligra, and development ones in area51 via CALLIGRA/editors/calligra.

Gentoo

Gentoo has Calligra packaged in Portage, tagged as unstable.

OpenSUSE

The easiest way to install Calligra on openSUSE is by going to the software.opensuse.org search.

Calligra packages are available from the KDE:Release:48 and KDE:Distro:Stable repositories for openSUSE 11.4 and 12.1.

Visit http://en.opensuse.org/KDE_repositories to find which repository fits your needs.

Ubuntu

Calligra 2.5 is available in the Kubuntu Backports PPA for 12.04 and comes as default with the development 12.10 (Quantal) version.

See http://www.kubuntu.org/news/calligra-2.5

ROSA Marathon 2012

ROSA Marathon provides Calligra in the contrib repository.

Windows

KO GmbH has released a Windows installer. Please go to the Download Page

The Windows version is in the works, and is at the moment, highly experimental. Not all applications or features known from the Linux/Unix version are included.

Unstable Release

Arch Linux

Arch Linux provides Calligra packages in the [extra] repository.

Fedora

Fedora packages are available in the rawhide development repo ([1]), and unofficial builds are available for prior releases from kde-unstable repo at [2] .

FreeBSD

Calligra ports are available in Area51.

openSUSE

Git snapshots are available from the unstable playground repository.

Daily build git snapshots are provided here (note a focus on mobile/Plasma Active for these packages)

Visit http://en.opensuse.org/KDE_repositories to find which repository fits your needs.

Ubuntu

Ubuntu users can get a nightly build of Calligra with the Project Neon, you need to add ppa:neon/ppa to your sources.list and install project-neon-calligra package.

Warning

"Be warned though, stuff here is REALLY unstable, we do not guarantee it will work all the time and won't eat you data, use at your own risk. Now that we have warned you, enjoy!" Project Neon wiki page

This script installs project neon and calligra:

sudo add-apt-repository ppa:neon/ppa \
 && sudo apt-get update\
 && sudo apt-get install project-neon-base \
   project-neon-calligra \
   project-neon-calligra-dbg

In order to run the installed packages you have to logout and choose "Project Neon" from the login screen. Neon always has the latest version, not necessarily the beta releases.

ROSA Marathon 2012

ROSA users can get the packages for development versions of Calligra from personal repository on ABF. To add it on your system run the following commands:

for i586 users

urpmi.addmedia ach_personal http://abf.rosalinux.ru/downloads/ach_personal/repository/rosa2012lts/i586/main/release

for x86_64 users

urpmi.addmedia ach_personal http://abf.rosalinux.ru/downloads/ach_personal/repository/rosa2012lts/x86_64/main/release

Debug Symbols

What are debugging symbols, and why are they important?

When a program is compiled with special switches to generate debugging symbols (the -g compiler switch) extra information is stored in the program file. This information can be used to generate a stack trace that contains much more information, such as the exact line number of the source file where things went wrong. Without this information it is very hard to figure out what went wrong by looking at the stack trace.

Note

Some distributions offer debug symbols in separate packages as listed below. Use them if you want to support the developers with better bug reports.

More info on back traces is available on KDE Techbase.

Debug symbols for Ubuntu/Debian

Please install package calligra-dbg to receive debug symbols for whole Calligra code.

Debug symbols for Fedora

As explained in the Installing debuginfo RPMs using yum section, use debuginfo-install calligra command.

@@ Line 38: / Line 38: @@
 The easiest way to install Calligra on openSUSE is by going to [http://software.opensuse.org/search?q=calligra&search_devel=false&search_unsupported=true&baseproject=ALL the software.opensuse.org search].
-* Calligra packages are available from the [https://build.opensuse.org/project/show?package=calligra&project=KDE:Release:48 KDE:Release:48] and [https://build.opensuse.org/project/show?package=calligra&project=KDE:UpdatedApps KDE:Distro:Stable] repositories for OpenSuse 11.4 and 12.1.
+* Calligra packages are available from the [https://build.opensuse.org/project/show?package=calligra&project=KDE:Release:48 KDE:Release:48] and [https://build.opensuse.org/project/show?package=calligra&project=KDE:UpdatedApps KDE:Distro:Stable] repositories for openSUSE 11.4 and 12.1.
 Visit [http://en.opensuse.org/KDE_repositories#What.27s_available http://en.opensuse.org/KDE_repositories] to find which repository fits your needs.
@@ Line 72: / Line 72: @@
 Calligra ports are available in [http://freebsd.kde.org/area51.php Area51].
-== OpenSUSE ==
+== openSUSE ==
 * Git snapshots are available from the [https://build.opensuse.org/project/show?package=calligra&project=KDE%3AUnstable%3APlayground unstable playground repository].
@@ Line 108: / Line 108: @@
 </nowiki>}}
-=== Debug Symbols ===
+= Debug Symbols =
-==== What are debugging symbols, and why are they important? ====
+== What are debugging symbols, and why are they important? ==
 When a program is compiled with special switches to generate debugging symbols (the -g compiler switch) extra information is stored in the program file. This information can be used to generate a stack trace that contains much more information, such as the exact line number of the source file where things went wrong. Without this information it is very hard to figure out what went wrong by looking at the stack trace.
@@ Line 118: / Line 118: @@
 More info on back traces is available on [http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Backtraces KDE Techbase].
-====Debug symbols for Ubuntu/Debian ====
+==Debug symbols for Ubuntu/Debian ==
 Please install package <code>calligra-dbg</code> to receive debug symbols for whole '''Calligra''' code.
-====Debug symbols for Fedora====
+==Debug symbols for Fedora==
 As explained in the [https://fedoraproject.org/wiki/StackTraces#Installing_debuginfo_RPMs_using_yum Installing debuginfo RPMs using yum] section, use <code>debuginfo-install calligra</code> command.
 [[Category:Office]]