public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Cc: Doug Henderson <djndnbvg@gmail.com>
Subject: Re: Up for adoption: ctags and expat
Date: Fri, 12 Aug 2016 13:57:00 -0000	[thread overview]
Message-ID: <20160812135738.ottxxjqtii2fktsm@calimero.vinschen.de> (raw)
In-Reply-To: <CAKf2h5St=KzXrQ1jQ=GF7zPYcnxSjszBp3iWMa13abHPbNZUcg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]

On Aug 12 15:41, Frank Fesevur wrote:
> 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.

Cool!  If you want to take over ctags and test universal ctags for
Cygwin, feel free if Warren agrees.  I'll change over maintainership
then.

Warren, does that sound good to you?

Doug, I hope you don't feel overlooked.  Expat is still yours if
Warren has no problems with that.

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

Huh, no, I didn't.  I doubt he wants to become Cygwin package
maintainer, though :)


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

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

Thread overview: 15+ 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
2016-08-12 13:57         ` Corinna Vinschen [this message]
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
2024-06-05 18:48               ` Jon Turney
2024-06-06  8:32                 ` Brian Inglis
2024-06-06 18:31                   ` [ITA] ctags Brian Inglis
2024-06-06 18:43                     ` Brian Inglis

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=20160812135738.ottxxjqtii2fktsm@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    --cc=djndnbvg@gmail.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).