Package Details: pology-git 0.13.r5484.4321df3d-1

Git Clone URL: https://aur.archlinux.org/pology-git.git (read-only, click to copy)
Package Base: pology-git
Description: A framework for custom processing of PO files.
Upstream URL: http://techbase.kde.org/Localization/Tools/Pology
Licenses: GPL3
Provides: pology
Replaces: pology-svn
Submitter: Gilrain
Maintainer: Gilrain
Last Packager: Gilrain
Votes: 8
Popularity: 0.002624
First Submitted: 2019-08-28 09:00
Last Updated: 2020-08-24 13:49

Dependencies (18)

Required by (1)

Sources (1)

Latest Comments

take100yen commented on 2020-08-07 05:58

The repository of Pology has been moved to https://invent.kde.org/sdk/pology.git

Gilrain commented on 2019-02-03 20:20

Should be fixed now. I used the official documentation as a template.

leper commented on 2019-02-03 17:49

The build failed for me with cmake complaining about no source dir being specified. Adding . to the cmake line solved that issue. Full diff below:

diff --git a/PKGBUILD b/PKGBUILD
index 3ffa9e5..6facb0b 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -35,7 +35,7 @@ prepare() {

 build() {
   cd ${srcdir}/pology
-  cmake -DCMAKE_INSTALL_PREFIX=/usr
+  cmake -DCMAKE_INSTALL_PREFIX=/usr .
   make
 }

Gilrain commented on 2017-08-17 09:57

Thanks for reporting it.
Unfortunately, there are two more upstream bugs during compilation:

-- Could NOT find DocbookXSL: Found unsuitable version "snapshot", but required is at least "1.75.2" (found /usr/share/xml/docbook/xsl-stylesheets-1.79.2)
-- Could NOT find Pygments: Found unsuitable version "", but required is at least "1.6" (found /usr/lib/python2.7/site-packages/pygments)

wget commented on 2017-08-13 19:36

You need to add community/python2-pyenchant to the depends array, otherwise it does not build.

Optional dependencies have to be updated as well.

Gilrain commented on 2012-03-23 09:57

When you upgrade, please be aware that pology-svn now resides in /usr instead of /opt.

Gilrain commented on 2011-02-05 23:31

Fixed, thank you.

unhammer commented on 2011-02-05 16:35

Shouldn't python-pyenchant be python2-pyenchant ?