FreeBSD Port: ctags-5.8
koobs.freebsd at gmail.com
Thu Oct 31 13:22:31 UTC 2013
On 1/11/2013 12:11 AM, Mathias Monnerville wrote:
> Hi Koobs,
> Debian-based distros have a package named `exuberant-ctags`. It's
> maintained by the Debian community, but I guess thoses patches are used
> accross other Linux distros as well. So, they provide one ctags to users,
> with some patches and enhancements (the Go support).
> I can't see any downside to this patch (with a low POLA): a few fixes and
> support for the Go language, which is nice :)
> Regarding port's naming, I agree -devel might sound a bit official, but
> thoses patches may be merged upstream someday... do you have any suggestion?
I think you're well positioned to decide, I thought I'd just ask some
questions to get the cogs turning :)
Also, top-posting makes it challenging for readers to track
conversations in mailing lists. For more info see:
A: Because it reverses the logical flow of conversation.
Q: Why is top posting frowned upon?
Looking forward to your PR :)
> 2013/10/31 Kubilay Kocak <koobs.freebsd at gmail.com>
>> On 31/10/2013 11:29 PM, Mathias Monnerville wrote:
>>> I know ctags 5.8 is the latest upstream stable version, but I'm aware of
>>> some nice patches and fixes labelled as ctags-5.9 in many GNU/Linux
>>> distros. For example, Debian
>>> chips a ctags-5.9~svn20110310 with the following changes (from
>>> exuberant-ctags (1:5.9~svn20110310-2) unstable; urgency=low
>>> * Add Go support, from a patch by Alexey Marinichev (closes: #634166).
>>> exuberant-ctags (1:5.9~svn20110310-1) unstable; urgency=low
>>> * New upstream release snapshot (thanks, Daniel Hahler; LP: #732860).
>>> - Fix crash with comments inside strings in OCaml (LP: #554898).
>>> * Drop accepted patches:
>>> - debian/patches/make-match-loop.patch
>>> - debian/patches/php-ignore-keywords-in-comments.patch
>>> * For Python, disable -i so imports are not tagged by default (thanks,
>>> Barry Warsaw; LP: #618979).
>>> * Upstream uses AC_SYS_LARGEFILE now, so drop explicit
>>> -D_FILE_OFFSET_BITS=64 in debian/rules.
>>> * Fix infinite loop parsing vim commands, when a non-alphanumeric
>>> character other than whitespace or '-' is found before the first
>>> alphanumeric character after 'command' (LP: #736367).
>>> It could be nice to also have Golang support in ctags on FreeBSD.
>>> I would be glad to open a PR for a new devel/ctags-devel port that I
>>> What do you think about it?
>>> Kind regards,
>>> freebsd-ports at freebsd.org mailing list
>>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>> Hi Mathias,
>> - Brings us closer to user-expectation parity
>> - More user choice & additional feature support
>> - You have put your hand up to contribute & maintain it (awesome!)
>> On naming:
>> - -devel may sound/seem like its more official than it is.
>> What is the package name in other OS's and how is it maintained? Do they
>> have 'one' ctags that just adds & rolls up the patches or two?
>> Also, are there any downsides to this patch set from a user or POLA
>> point of view? The answer this may help you determine what course of
>> action to take
More information about the freebsd-ports