Re: ITP: cscope -- Interactively examine a C program source

2012-10-29 Thread Corinna Vinschen
On Oct 28 22:00, Dave And Diane wrote:
 Hi Corinna,
 
 Thanks for doing this - the past week got away from me.

No worries.  Are you going to create a mail to the cygwin-announce list?

 On 10/21/2012 5:18 AM, Corinna Vinschen wrote:
 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

Thanks,
Corinna


P.S: A bit less http://cygwin.com/acronyms/#TOFU would be nice, though...


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


Re: ITP: cscope -- Interactively examine a C program source

2012-10-21 Thread Corinna Vinschen
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


Re: ITP: cscope -- Interactively examine a C program source

2012-10-20 Thread Dave And Diane


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




--

Diane  Dave
http://www.velvetstarbears.com/  http://www.kringlecottage.com/
Fortune: The difference between America and England is that the
English think 100 miles is a long distance and the Americans
think 100 years is a long time.



Re: ITP: cscope -- Interactively examine a C program source

2012-10-15 Thread Corinna Vinschen
Hi Dave,
Hi Jari,

On Oct 14 13:56, Dave And Diane wrote:
 Effectively yes. I'm cool with mlcscope being removed from the
 package list when cscope appears.

Three followup questions:

- Does mlcscope provide functionality cscode doesn't?  That might
  be a point in favor of keeping it alive, unless you think it's
  not that important.

- If we obsolete mlcscope, would it make sense to create a new, empty
  mlcscope package which requires cscope so that cscope is automatically
  replacing mlcscope in existing installations?

- If so, would it also make sense if the cscope package creates a
  mlcscope symlink - cscope to help people along which use mlcsope in
  scripts (if that makes any sense at all??


Thanks,
Corinna

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


Re: ITP: cscope -- Interactively examine a C program source

2012-10-14 Thread Dave And Diane
Effectively yes. I'm cool with mlcscope being removed from the package 
list when cscope appears.


Cheers
Dave

On 10/9/2012 6:07 AM, Corinna Vinschen wrote:

Hi guys,

On Oct  7 08:26, Dave And Diane wrote:

Hi Jari,

Yes, mlcscope was from 2006, and it also came from the Lucent
exptools source tree which is a different version than the gnu
cscope. Lucent has since stopped distributing mlcscope so I think
putting cscope in the packaging is a good thing. I've thought about
doing it myself - but hadn't got to it - glad you have followed this
path.

does that mean cscope obsoletes mlcscope?


Corinna




--

Diane  Dave
http://www.velvetstarbears.com/  http://www.kringlecottage.com/
Fortune: The difference between America and England is that the
English think 100 miles is a long distance and the Americans
think 100 years is a long time.



Re: ITP: cscope -- Interactively examine a C program source

2012-10-09 Thread Corinna Vinschen
On Oct  8 13:44, marco atzeri wrote:
 On 9/30/2012 11:20 AM, Jari Aalto wrote:
 
 wget --recursive --no-host-directories --cut-dirs=3 \
  
  http://cante.net/~jaalto/tmp/cygwin/cscope/cscope-15.8.0.1-1-src.tar.bz2 \
  http://cante.net/~jaalto/tmp/cygwin/cscope/cscope-15.8.0.1-1.tar.bz2 \
  http://cante.net/~jaalto/tmp/cygwin/cscope/setup.hint
 
  # To check packaging
 
  cd cscope
  tar -xf *-src.tar.bz2
  ./*.sh --color --verbose all
 
 Included in Debian:
 
  http://packages.debian.org/cscope
 
 Notes:
 
  This is the original version released 2012-08-04. The mlscope included
  in Cygwin is probably from 2006[*]
 
 Jari
 
 
 it builds and packages fine. GTG
 
 Regards
 Marco
 

Uploaded.


Thanks,
Corinna

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


Re: ITP: cscope -- Interactively examine a C program source

2012-10-09 Thread Corinna Vinschen
Hi guys,

On Oct  7 08:26, Dave And Diane wrote:
 Hi Jari,
 
 Yes, mlcscope was from 2006, and it also came from the Lucent
 exptools source tree which is a different version than the gnu
 cscope. Lucent has since stopped distributing mlcscope so I think
 putting cscope in the packaging is a good thing. I've thought about
 doing it myself - but hadn't got to it - glad you have followed this
 path.

does that mean cscope obsoletes mlcscope?


Corinna

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


Re: ITP: cscope -- Interactively examine a C program source

2012-10-09 Thread Jari Aalto
On 2012-10-09 13:07, Corinna Vinschen wrote:
| Hi guys,
|
| On Oct  7 08:26, Dave And Diane wrote:
|  Hi Jari,
| 
|  Yes, mlcscope was from 2006, and it also came from the Lucent
|  exptools source tree which is a different version than the gnu
|  cscope. Lucent has since stopped distributing mlcscope so I think
|  putting cscope in the packaging is a good thing. I've thought about
|  doing it myself - but hadn't got to it - glad you have followed this
|  path.
|
| does that mean cscope obsoletes mlcscope?

Not knowing mlscope, so I'm guessing, but it probably does as mlscope was a
spin-off.

Jari


Re: ITP: cscope -- Interactively examine a C program source

2012-10-08 Thread marco atzeri

On 9/30/2012 11:20 AM, Jari Aalto wrote:


wget --recursive --no-host-directories --cut-dirs=3 \
 http://cante.net/~jaalto/tmp/cygwin/cscope/cscope-15.8.0.1-1-src.tar.bz2 \
 http://cante.net/~jaalto/tmp/cygwin/cscope/cscope-15.8.0.1-1.tar.bz2 \
 http://cante.net/~jaalto/tmp/cygwin/cscope/setup.hint

 # To check packaging

 cd cscope
 tar -xf *-src.tar.bz2
 ./*.sh --color --verbose all

Included in Debian:

 http://packages.debian.org/cscope

Notes:

 This is the original version released 2012-08-04. The mlscope included
 in Cygwin is probably from 2006[*]

Jari



it builds and packages fine. GTG

Regards
Marco




Re: ITP: cscope -- Interactively examine a C program source

2012-10-07 Thread Dave And Diane

Hi Jari,

Yes, mlcscope was from 2006, and it also came from the Lucent exptools 
source tree which is a different version than the gnu cscope. Lucent has 
since stopped distributing mlcscope so I think putting cscope in the 
packaging is a good thing. I've thought about doing it myself - but 
hadn't got to it - glad you have followed this path.


Cheers
Dave
On 9/30/2012 4:20 AM, Jari Aalto wrote:

wget --recursive --no-host-directories --cut-dirs=3 \
 http://cante.net/~jaalto/tmp/cygwin/cscope/cscope-15.8.0.1-1-src.tar.bz2 \
 http://cante.net/~jaalto/tmp/cygwin/cscope/cscope-15.8.0.1-1.tar.bz2 \
 http://cante.net/~jaalto/tmp/cygwin/cscope/setup.hint

 # To check packaging

 cd cscope
 tar -xf *-src.tar.bz2
 ./*.sh --color --verbose all

Included in Debian:

 http://packages.debian.org/cscope

Notes:

 This is the original version released 2012-08-04. The mlscope included
 in Cygwin is probably from 2006[*]

Jari

[ setup.hint ]

sdesc: Interactively examine a C program source
ldesc: A source browsing tool. Although it is primarily designed to search C
code (including lex and yacc files), it can also be used for C++ code.
Using cscope, you can easily search for where symbols are used and
defined.
category: Devel
requires: libncurses10


[*] http://www.lowtechnet.com/cscope/




--

Diane  Dave
http://www.velvetstarbears.com/  http://www.kringlecottage.com/
Fortune: The difference between America and England is that the
English think 100 miles is a long distance and the Americans
think 100 years is a long time.