Package Details: global 6.5.4-2

Git Clone URL: https://aur.archlinux.org/global.git (read-only)
Package Base: global
Description: A source code tag system
Upstream URL: http://www.gnu.org/software/global/
Licenses: GPL
Submitter: None
Maintainer: ptrv
Last Packager: ptrv
Votes: 89
Popularity: 4.382572
First Submitted: 2007-03-05 00:02
Last Updated: 2016-04-10 17:53

Required by (2)

Sources (1)

Latest Comments

ptrv commented on 2016-04-10 17:54

@blueyed Added global patch to use lid-idutils executable

blueyed commented on 2016-04-06 11:10

`lid` from idutils in Arch is installed as `idutils-lid` (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=idutils#n30).

There does not appear to be a `--with-idutils(-lid)` option (should be proposed upstream probably?!) to specify the non-default location.
For now, global could be patched in Arch to use the `idutils-lid` program/location?

chopps commented on 2016-02-25 09:45

+1 on changing python2 to python (remove dependency and udpate to python-pygments). It just works and eliminates the python2 requirement.

eagletmt commented on 2016-01-11 02:20

Please add python2 to the makedepends array.
python2 is required to make the package.

NoSuck commented on 2015-04-13 05:12

Pity this isn't an official package anymore, as gtags seems to be superior to ctags in every respect.

Szunti commented on 2015-04-06 01:51

Why not delete the PYTHON=python2? It works with python3.
This also need a change of python2-pygments to python-pygments in dependencies.

tsdh commented on 2015-03-25 05:07

What's the relation between this package and the global package?

https://aur.archlinux.org/packages/global/

It looks to me like it's the very same, no? And the official name of gtags is GNU Global, so IMO the other package (which also has a much longer history) is the canonical one to be used.

torpesco commented on 2015-03-24 17:24

pkgver=6.4
md5sums=('34987ce863661bfceddc1ac016d19195')
sha256sums=('315bf69bf2b4dbe661ff2800967e5f1171edfb83a0f17424612baa673aff248e')

j.moyerman commented on 2015-02-05 18:16

With new version of automake in Arch repo's. It's necessary to rerun autoreconf in the build step.

build() {
cd "${srcdir}/${pkgname}-${pkgver}"
autoreconf -fi
PYTHON=/usr/bin/python2 ./configure --prefix=/usr --with-exuberant-ctags=/usr/bin/ctags
make
}

in PKGBUILD

hav3lock commented on 2015-01-17 01:13

@naquad, kk. As for `reconf.sh`, lol, the diff did its job: I was curious as to whether it was necessary since it was unusual and confusing, especially given that the INSTALL file never mentioned it, although I didn't grep, I just skimmed through it.

Like I said, though, I apologize if I've been kind of a dick: nobody likes being told what to do or how they should be doing them.

All comments