From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: ITP: cscope -- Interactively examine a C program source
Date: Sun, 21 Oct 2012 10:18:00 -0000 [thread overview]
Message-ID: <20121021101842.GB4574@calimero.vinschen.de> (raw)
In-Reply-To: <508339C3.60209@kringlecottage.com>
On Oct 20 18:54, Dave And Diane wrote:
>
> Yep. Will do
>
> Cheers
> Dave
> On 10/20/2012 6:20 AM, Corinna Vinschen wrote:
> >On Oct 19 22:37, Dave And Diane wrote:
> >>Hi Corinna,
> >>
> >>mlcscope does provide some differences - it was designed to be
> >>multi-lingual rather than assume C style parsing rules and a few
> >>menus were different.
> >>
> >>Unfortunately it never evolved beyond the initial implementation and
> >>I doubt that anyone would notice.
> >>
> >>Normally, yes creating a package dependency and a link from mlcscope
> >>to cscope would be a good idea and I would encourage that. I must
> >>admit though, I don't actually know of anyone using mlcscope so I'm
> >>not sure it will actually help anyone. I'd love to be proven wrong -
> >>perhaps it was wildly popular and I didn't know it ;-) If you think
> >>its worth continuing on this path to be safe, I'll be happy to help.
> >Ok... I guess, what we can do is simply to obsolete mlcscope. I'd
> >create an empty new package and tweak the setup.hint file to require
> >cscope. After that it would be nice if you could just create a short
> >announcement that mlcscope has been replaced by cscope and mlcscope
> >gets discontinued.
> >
> >Does that make sense?
> >
> >
> >Corinna
> >
Ok, I created an emtpy mlcscope-99-1 package and changed setup.hint
like this:
sdesc: "Obsolete Lucent version of cscope"
ldesc: "Obsolete Lucent version of cscope"
requires: cscope
category: _obsolete
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2012-10-21 10:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 9:20 Jari Aalto
2012-10-07 13:26 ` Dave And Diane
2012-10-09 11:07 ` Corinna Vinschen
2012-10-09 11:24 ` Jari Aalto
2012-10-14 18:56 ` Dave And Diane
2012-10-15 8:18 ` Corinna Vinschen
2012-10-20 3:37 ` Dave And Diane
2012-10-20 11:22 ` Corinna Vinschen
2012-10-20 23:54 ` Dave And Diane
2012-10-21 10:18 ` Corinna Vinschen [this message]
2012-10-29 3:00 ` Dave And Diane
2012-10-29 8:50 ` Corinna Vinschen
2012-10-08 11:44 ` marco atzeri
2012-10-09 11:06 ` 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=20121021101842.GB4574@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).