From owner-freebsd-ports@FreeBSD.ORG Thu Oct 31 13:22:31 2013 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F2F58BC; Thu, 31 Oct 2013 13:22:30 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C442B2C3E; Thu, 31 Oct 2013 13:22:30 +0000 (UTC) Received: by mail-pa0-f44.google.com with SMTP id fb1so2487081pad.17 for ; Thu, 31 Oct 2013 06:22:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=pcJFXSuKtXcIgVkE2grZYgiKvLyL98dCho92oCWGsuQ=; b=gzpYAsB7uDlVqeENcDwFheCBX1U4Mud7QmGl5FspMAgLm5Xfa1MV0SlNcUIv8IVK2z uCwoQOrP2HJecjBqQ9n+SFdQRlYH+eLIvv/Vf0moCsLA/vUPd4MFOYXCGE4IrRqqcCsV ZS7NvxeC6RICqYl9p+lvcUMVaOg3Hksmy3AVKqggMxPtSnCKbmJiQ+i+wI1Qd85FiJ1z iNzwAkzdJV56vO8JkIiTTsJGEysze/RVv88EdVaCUKyR9Mw6nMNshf97xn7HMPMJAobr YLXCPJTURa1pPaKCxlQYOC30Netr/InG8AAFhGBNyUOvuW4sv5H0lXhkgufgteP73mU9 Vz4Q== X-Received: by 10.69.25.38 with SMTP id in6mr1882266pbd.178.1383225750425; Thu, 31 Oct 2013 06:22:30 -0700 (PDT) Received: from [192.168.1.7] (ppp59-167-128-11.static.internode.on.net. [59.167.128.11]) by mx.google.com with ESMTPSA id rv9sm4220487pbc.4.2013.10.31.06.22.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 31 Oct 2013 06:22:29 -0700 (PDT) Message-ID: <5272598C.90607@FreeBSD.org> Date: Fri, 01 Nov 2013 00:22:20 +1100 From: Kubilay Kocak User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Thunderbird/25.0 MIME-Version: 1.0 To: Mathias Monnerville Subject: Re: FreeBSD Port: ctags-5.8 References: <5272519B.4040601@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports , zeising X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: koobs@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Oct 2013 13:22:31 -0000 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? > > Mathias 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: https://www.freebsd.org/doc/en/articles/mailing-list-faq/etiquette.html#idp75086000 A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? Looking forward to your PR :) Koobs > 2013/10/31 Kubilay Kocak > >> On 31/10/2013 11:29 PM, Mathias Monnerville wrote: >>> Hello, >>> >>> 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 >>> /usr/share/doc/exuberant-ctags/changelog.Debian.gz): >>> >>> 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 >> would >>> maintain. >>> >>> What do you think about it? >>> >>> Kind regards, >>> Mathias >>> _______________________________________________ >>> freebsd-ports@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >>> >> >> Hi Mathias, >> >> Positives: >> >> - 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 >> >> Koobs >> >