public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Frank Fesevur <ffes@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: Up for adoption: ctags and expat
Date: Fri, 12 Aug 2016 13:42:00 -0000	[thread overview]
Message-ID: <CAKf2h5St=KzXrQ1jQ=GF7zPYcnxSjszBp3iWMa13abHPbNZUcg@mail.gmail.com> (raw)
In-Reply-To: <20160812101917.dfi7yv3vdfujc3kq@calimero.vinschen.de>

2016-08-12 12:19 GMT+02:00 Corinna Vinschen:
> On Aug 12 11:01, Frank Fesevur wrote:
>> Universal ctags is the continuation of exuberant ctags. We have tried
>> to convince Darren Hiebert (the original author of exuberant) to team
>> up so we could keep the name. But that didn't work out, so we had to
>> fork and came up with the name universal.
>
> Pity.

Absolutely.

>> I would say, make the switch to universal. I am willing to maintain
>> that package. Question is how to update a package without official
>> releases. And it hasn't been included in any major distro AFAIK.
>
> You could start with a test build and set the version numbers in the
> setup.hint file explicitely.  If it works out fine, you only have to
> keep up with the prev/curr markers as long as "prev" is the exuberant
> package.  Question is, *are* there any version numbers yet?  If not,
> you could use git commit IDs for the time being.

There is no version number yet. The expectation is it will become 6.0
so something like 5.9-date-shorthash could a temporary version number
for a test release. The compile date and hash are shown when "ctags
--version" is invoked.

I just tried and the basic compilation of the current master branch works.

Regards,
Frank

BTW. Did you know that a coworker of you is the lead developer of
universal ctags? https://github.com/masatake

  reply	other threads:[~2016-08-12 13:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 23:49 Warren Young
2016-08-12  5:33 ` Doug Henderson
2016-08-12  8:12 ` Corinna Vinschen
2016-08-12  9:02   ` Frank Fesevur
2016-08-12 10:19     ` Corinna Vinschen
2016-08-12 13:42       ` Frank Fesevur [this message]
2016-08-12 13:57         ` Corinna Vinschen
2016-08-12 17:57           ` Warren Young
2016-08-12 19:02             ` Doug Henderson
2016-08-12 19:43               ` Corinna Vinschen
2016-08-12 19:41             ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKf2h5St=KzXrQ1jQ=GF7zPYcnxSjszBp3iWMa13abHPbNZUcg@mail.gmail.com' \
    --to=ffes@users.sourceforge.net \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).