Package Details: ctags-git 6.0.0.r525.gc480d71e1-1

Git Clone URL: https://aur.archlinux.org/ctags-git.git (read-only, click to copy)
Package Base: ctags-git
Description: Generates an index file of language objects found in source files
Upstream URL: https://ctags.io/
Licenses: GPL
Conflicts: ctags
Provides: ctags
Submitter: polyzen
Maintainer: Chocobo1
Last Packager: Chocobo1
Votes: 60
Popularity: 0.000000
First Submitted: 2021-01-14 17:35 (UTC)
Last Updated: 2023-11-23 19:27 (UTC)

Required by (59)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

J5lx commented on 2018-06-07 11:10 (UTC)

@cbb I see your point, but ctags is what upstream chose and I’m not exactly a fan of making more downstream changes than necessary – just like the TUs are advised not to include any patches in official packages that have not been accepted into upstream. Besides, ctags is often used internally by other tools and some of them might not allow changing the binary used.

Jesse2004 commented on 2018-06-07 02:59 (UTC)

This package should be in the official repository...

cbb commented on 2018-06-02 11:36 (UTC) (edited on 2018-06-02 11:43 (UTC) by cbb)

Any chance we could rename /usr/bin/ctags to /usr/bin/uctags and remove conflicts=('ctags')? Many distros still only package the original ctags and it's useful to be able to install both on Arch for testing compatibility etc.

J5lx commented on 2018-02-14 15:37 (UTC)

That's right, but those packages are in base-devel and thus assumed to be installed and not explicitly listed.

polm23 commented on 2018-02-14 13:42 (UTC)

This depends on autoconf and automake.

maximbaz commented on 2017-11-02 22:51 (UTC)

Please replace "mkdir" with "mkdir -p", otherwise the build fails unless I remove the old temporary files created since the last build: ==> Starting check()... mkdir: cannot create directory ‘/tmp/makepkg/universal-ctags-git/src/testhome’: File exists ==> ERROR: A failure occurred in check(). Aborting... Error installing universal-ctags-git : exit status 1

cbb commented on 2017-08-31 19:32 (UTC)

Disregard my previous comment -- I thought the tests were super slow to run but I think the test runner just got stuck the first time I tried. On second attempt they actually seem fast enough to not really matter.

cbb commented on 2017-08-31 19:24 (UTC)

Surely check() should just be a small subset of tests to check the build is working correctly. What's the point of running the full test suite when upstream already does that for every commit via CI?

blueyed commented on 2017-07-01 23:21 (UTC)

I've added "!check" now to to `BUILDENV` in `/etc/makepkg.conf`, which helps here. Thanks for addressing the HOME issue.

J5lx commented on 2017-06-26 13:19 (UTC)

Regarding check, see https://wiki.archlinux.org/index.php/Creating_packages#check.28.29. In short, it is highly recommended to use it and users who don’t want that can disable it on their system in makepkg.conf. I’ll do something about HOME, though.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »