Package Details: sword-svn 3:1.9.0.svnversion.3887-1

Git Clone URL: https://aur.archlinux.org/sword-svn.git (read-only, click to copy)
Package Base: sword-svn
Description: Libraries for Bible programs - svn-version
Upstream URL: http://crosswire.org/sword/
Keywords: bible
Licenses: GPL
Conflicts: sword
Provides: sword
Submitter: haawda
Maintainer: None
Last Packager: haawda
Votes: 20
Popularity: 0.000000
First Submitted: 2012-02-18 11:12 (UTC)
Last Updated: 2023-02-19 12:14 (UTC)

Required by (15)

Sources (1)

Pinned Comments

haawda commented on 2023-02-19 12:18 (UTC) (edited on 2023-02-19 12:18 (UTC) by haawda)

I added a check function, but be careful.

UUpstream warnes: IF YOU LIVE IN A PERSECUTED COUNTRY AND DO NOT WISH TO RISK DETECTION, YOU SHOULD NOT USE INSTALL MANAGER'S REMOTE SOURCE FEATURES.

So use makepkg --nocheck in that case.

Latest Comments

1 2 3 4 Next › Last »

haawda commented on 2023-02-19 12:18 (UTC) (edited on 2023-02-19 12:18 (UTC) by haawda)

I added a check function, but be careful.

UUpstream warnes: IF YOU LIVE IN A PERSECUTED COUNTRY AND DO NOT WISH TO RISK DETECTION, YOU SHOULD NOT USE INSTALL MANAGER'S REMOTE SOURCE FEATURES.

So use makepkg --nocheck in that case.

haawda commented on 2022-08-02 14:08 (UTC)

The subversion repo is up again.

haawda commented on 2022-08-01 23:00 (UTC)

The subversion repo seems to have a problem - hopfully temporary. A woraround is to use the unofficial git repo 

# Maintainer: Stefan Husmann <stefan-husmann@t-online.de>

pkgname=sword-git
pkgver=1.9.0.svnversion.r3697
pkgrel=1
pkgdesc="Libraries for Bible programs - svn-version"
arch=('i686' 'x86_64')
url="http://www.crosswire.org/sword/"
license=('GPL')
depends=('curl' 'clucene' 'xapian-core')
makedepends=('git')
provides=('sword=1.9.1')
conflicts=('sword')
source=("$pkgname::git+https://github.com/bibletime/crosswire-sword-mirror.git")
sha256sums=('SKIP')

pkgver() {
  cd "${pkgname}"
  printf "%s.r%s" $(awk '/AC_INIT/ {print $2}' configure.ac | tr -d ,) $(git rev-list --count HEAD)
}

build() {
  cd "${pkgname}"
  ./autogen.sh
  CXXFLAGS+=' -DU_USING_ICU_NAMESPACE=1'
  ./configure --prefix=/usr --libdir=/usr/lib --sysconfdir=/etc --without-icu 
  make
}

package() {
  cd "${pkgname}"
  make DESTDIR="$pkgdir/" install
  make DESTDIR="$pkgdir/" install_config
}

haawda commented on 2021-12-12 16:56 (UTC)

aleque, I think no. This needs to be fixed upstream.

alerque commented on 2021-12-11 21:32 (UTC)

Anything I need to do the Xiphos build in my repository to make this work with a current version (as opposed to the older pinned version)?

haawda commented on 2021-04-06 19:10 (UTC)

I sticked to version r3844 because xiphos failed to build against r3845. But now it fails anyway.

alerque commented on 2021-04-06 05:23 (UTC)

Please remove the versioning from the conflicts line, that is preventing swapping out the sword package as an upgrade without uninstalling this and other dependencies first. I think the versioned provides is fine, but the conflicts should be generic unversioned.

alerque commented on 2020-04-19 20:40 (UTC)

Re your earlier comment:

I hate that "r" in version numbers. I see no point in having it.

It serves several purposes. In Arch's version checking scheme 3 > r55 because anything that starts with r is considered lower than numbers. This means you can transition to proper upstream versioning withouth having to add an epoch. It also serves to mark where the upstream versioning ends and the arch local counter stuff begins. Please go back to using it per Arch wiki guidelines.

alerque commented on 2020-04-19 20:35 (UTC)

Can you please fix the pkgver and provides so they are actually relative to the last release point? This should be something like 1.8.1-r400 where the last bit is an increment since the 1.8.1 release.

As it is it is impossible to fix the xiphos-git package so that it requires sword>1.8.1 such that it will use the -svn package for now and automatically allow the stable package to fulfill the dependency when 1.8.2 is released.

haawda commented on 2017-05-18 02:52 (UTC)

I tried to report this to the mailing list, but my mail did not pass the moderator. In the meanwhile I fixed it myself with a patch.

1 2 3 4 Next › Last »