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: Frank Fesevur <ffes@users.sourceforge.net>
Subject: Re: Up for adoption: ctags and expat
Date: Fri, 12 Aug 2016 08:12:00 -0000	[thread overview]
Message-ID: <20160812081156.ea3ylmngpojeub72@calimero.vinschen.de> (raw)
In-Reply-To: <8B595AA4-99A0-4497-9D8B-AF27D79B28A0@etr-usa.com>

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

On Aug 11 17:49, Warren Young wrote:
> I’m the current maintainer of these two packages.  As it happens,
> I have never seriously used either under Cygwin.  I only adopted
> ctags because it was abandoned in 2003 and was in danger of being
> removed from the distribution after repeated attempts to contact its
> maintainer in 2005 failed.  Since I do use ctags on other platforms,
> I decided that I was at least in a position to keep it in Cygwin,
> so I adopted it.  The situation was less drastic with expat: I simply
> took over the package’s maintenance when Brian Dessent stepped down
> in 2008.
> 
> The time has come for someone else to maintain these packages.
> 
> But not just anyone.  I do not want to drop another twig onto the
> back of someone who’s already carrying a lot for the Cygwin project.
> I’d prefer that these packages to go to someone who’s been looking
> to jump into Cygwin package maintainership, and has just been waiting
> for an excuse. 
> 
> These two are a mixed bag when it comes to ease of maintainership, 
> each for very different reasons.
> 
> The easy part with ctags is that there hasn’t been an upstream 
> release since 2009, and there is no reason to expect that there will 
> be another.  The hard part is that the shipped Makefile doesn’t
> understand how to do out-of-tree builds, something Cygport expects
> to be able to do, so I had to write a custom build script to produce 
> the current packages, which might have to be adjusted by the next
> maintainer of this package, if a new version comes out with the same
> primitive build system. 

Given the obvious lack of upstream development, did anybody try
to replace exuberant ctags with universal ctags?

  https://ctags.io/

I noticed that our co-maintainer Frank Fesevur is involved in this
project.  Frank, any insight?


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 --]

  parent reply	other threads:[~2016-08-12  8:12 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 [this message]
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
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=20160812081156.ea3ylmngpojeub72@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    --cc=ffes@users.sourceforge.net \
    /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).