[pkgsrc/trunk]: pkgsrc/doc Update to exctags to 5.5.4.

[uebayasi <uebayasi%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/c7873fa3ee3d
branches:  trunk
changeset: 476103:c7873fa3ee3d
user:      uebayasi <uebayasi%pkgsrc.org@localhost>
date:      Thu Jun 03 15:20:59 2004 +0000

description:
Update to exctags to 5.5.4.

Changes since 5.5.0:

* Added support for Perl labels.
* Added support for Perl "use constant" [Perl, Patch #853704, Feature Request
  #710017].
* Added support for package qualification of tags, removing useless "package"
  tag kind [Perl, Feature Request #448887].
* Added support for "and" keyword [SML, Bug #816636].
* Added support for variables [PHP].
* Added tags for local variables for C-based languages [C/C++/C#/Java/Vera,
  Feature Request #449503].
* Added support for tags for labels [PL/SQL].
* Added support for tags for constant definitions [PHP].

And many bug fixes.

diffstat:

 devel/exctags/Makefile         |   17 +-
 devel/exctags/distinfo         |    9 +-
 devel/exctags/patches/patch-aa |   31 +-
 devel/exctags/patches/patch-ab |  395 -----------------------------------------
 doc/CHANGES                    |    3 +-
 5 files changed, 36 insertions(+), 419 deletions(-)

diffs (truncated from 549 to 300 lines):

diff -r e7400d387087 -r c7873fa3ee3d devel/exctags/Makefile
--- a/devel/exctags/Makefile    Thu Jun 03 12:37:40 2004 +0000
+++ b/devel/exctags/Makefile    Thu Jun 03 15:20:59 2004 +0000
@@ -1,7 +1,7 @@
-# $NetBSD: Makefile,v 1.9 2004/04/27 03:09:58 snj Exp $
+# $NetBSD: Makefile,v 1.10 2004/06/03 15:20:59 uebayasi Exp $
 #
 
-DISTNAME=      ctags-5.5
+DISTNAME=      ctags-5.5.4
 PKGNAME=       ex${DISTNAME}
 CATEGORIES=    devel
 MASTER_SITES=  ${MASTER_SITE_SOURCEFORGE:=ctags/}
@@ -10,6 +10,8 @@
 HOMEPAGE=      http://ctags.sourceforge.net/
 COMMENT=       Exuberant (feature-filled) tagfile generator for vi, emacs and clones
 
+PKG_INSTALLATION_TYPES=        overwrite pkgviews
+
 USE_BUILDLINK3=                yes
 GNU_CONFIGURE=         # defined
 CONFIGURE_ARGS+=       --enable-macro-patterns
@@ -18,4 +20,15 @@
 
 CPPFLAGS+=             -DETAGS='\"exetags\"'
 
+SUBST_CLASSES+=                man
+SUBST_STAGE.man=       post-patch
+SUBST_FILES.man=       ctags.1
+SUBST_SED.man= \
+       -e 's|^ctags \\-|exctags \\-|' \
+       -e 's|fBctags|fBexctags|g' \
+       -e 's|fBetags|fBexetags|g' \
+       -e 's|"ctags|"exctags|g' \
+       -e 's|"etags|"exetags|g' \
+       -e 's|/usr/local|${LOCALBASE}|g'
+
 .include "../../mk/bsd.pkg.mk"
diff -r e7400d387087 -r c7873fa3ee3d devel/exctags/distinfo
--- a/devel/exctags/distinfo    Thu Jun 03 12:37:40 2004 +0000
+++ b/devel/exctags/distinfo    Thu Jun 03 15:20:59 2004 +0000
@@ -1,6 +1,5 @@
-$NetBSD: distinfo,v 1.6 2003/04/07 09:30:42 seb Exp $
+$NetBSD: distinfo,v 1.7 2004/06/03 15:20:59 uebayasi Exp $
 
-SHA1 (ctags-5.5.tar.gz) = 9e69d653d7847ec22150c4a20705576944fb5bbd
-Size (ctags-5.5.tar.gz) = 241089 bytes
-SHA1 (patch-aa) = 7a482534cd0c560df436f45ae3b697f6b07ef534
-SHA1 (patch-ab) = 592f13430e6d7e2f4574cfcdb924f3bc9502a5e3
+SHA1 (ctags-5.5.4.tar.gz) = 1f912ef66c44d5527ce44c447a13fc33188bf16e
+Size (ctags-5.5.4.tar.gz) = 260962 bytes
+SHA1 (patch-aa) = 1e5bf6c9df7b4d905c18ad6512dd9f54ca1e1ce2
diff -r e7400d387087 -r c7873fa3ee3d devel/exctags/patches/patch-aa
--- a/devel/exctags/patches/patch-aa    Thu Jun 03 12:37:40 2004 +0000
+++ b/devel/exctags/patches/patch-aa    Thu Jun 03 15:20:59 2004 +0000
@@ -1,7 +1,7 @@
-$NetBSD: patch-aa,v 1.3 2002/03/06 16:45:02 seb Exp $
+$NetBSD: patch-aa,v 1.4 2004/06/03 15:20:59 uebayasi Exp $
 
---- Makefile.in.orig   Sun Feb 17 22:42:06 2002
-+++ Makefile.in
+--- Makefile.in.orig   2004-06-03 23:33:10.000000000 +0900
++++ Makefile.in        2004-06-03 23:37:34.000000000 +0900
 @@ -6,8 +6,8 @@
  # These are the names of the installed programs, in case you wish to change
  # them.
@@ -17,7 +17,7 @@
  CC    = @CC@
  DEFS  = @DEFS@
  CFLAGS        = @CFLAGS@
-+CPPFLAGS = @CPPFLAGS@
++CPPFLAGS      = @CPPFLAGS@
  LDFLAGS       = @LDFLAGS@
  LIBS  = @LIBS@
  EXEEXT        = @EXEEXT@
@@ -28,9 +28,9 @@
 -INSTALL               = cp
 -INSTALL_PROG  = $(INSTALL)
 -INSTALL_DATA  = $(INSTALL)
-+INSTALL_PROGRAM = $(BSD_INSTALL_PROGRAM)
-+INSTALL_MAN     = $(BSD_INSTALL_MAN)
-+INSTALL_DATA    = $(BSD_INSTALL_DATA)
++INSTALL_PROGRAM       = $(BSD_INSTALL_PROGRAM)
++INSTALL_MAN   = $(BSD_INSTALL_MAN)
++INSTALL_DATA  = $(BSD_INSTALL_DATA)
  
  READ_LIB = readtags.$(OBJEXT)
  READ_INC = readtags.h
@@ -51,39 +51,38 @@
  
  $(OBJECTS): $(HEADERS) config.h
  
-@@ -138,8 +139,7 @@
+@@ -138,7 +139,7 @@
  install-lib: $(DEST_READ_LIB) $(DEST_READ_INC)
  
  $(DEST_CTAGS): $(CTAGS_EXEC) $(bindir) FORCE
 -      $(INSTALL_PROG) $(CTAGS_EXEC) $@  &&  chmod 755 $@
--      $(STRIP) $(DEST_CTAGS)
-+      $(INSTALL_PROGRAM) $(CTAGS_EXEC) $@
++      $(INSTALL_PROGRAM) $(CTAGS_EXEC) $@  &&  chmod 755 $@
  
  $(DEST_ETAGS):
        - if [ -x $(DEST_CTAGS) ]; then \
-@@ -154,7 +154,7 @@
+@@ -153,7 +154,7 @@
  install-eman: $(DEST_EMAN)
  
  $(DEST_CMAN): $(man1dir) $(MANPAGE) FORCE
 -      - $(INSTALL_DATA) $(srcdir)/$(MANPAGE) $@  &&  chmod 644 $@
-+      - $(INSTALL_MAN) $(srcdir)/$(MANPAGE) $@
++      - $(INSTALL_MAN) $(srcdir)/$(MANPAGE) $@  &&  chmod 644 $@
  
  $(DEST_EMAN):
        - if [ -f $(DEST_CMAN) ]; then \
-@@ -165,10 +165,10 @@
+@@ -164,10 +165,10 @@
  # install the library
  #
  $(DEST_READ_LIB): $(READ_LIB) $(libdir) FORCE
 -      $(INSTALL_PROG) $(READ_LIB) $@  &&  chmod 644 $@
-+       $(INSTALL_DATA) $(READ_LIB) $@
++      $(INSTALL_DATA) $(READ_LIB) $@  &&  chmod 644 $@
  
  $(DEST_READ_INC): $(READ_INC) $(incdir) FORCE
 -      $(INSTALL_PROG) $(READ_INC) $@  &&  chmod 644 $@
-+      $(INSTALL_DATA) $(READ_INC) $@
++      $(INSTALL_DATA) $(READ_INC) $@  &&  chmod 644 $@
  
  
  #
-@@ -217,6 +217,6 @@
+@@ -216,6 +217,6 @@
  # implicit rules
  #
  .c.$(OBJEXT):
diff -r e7400d387087 -r c7873fa3ee3d devel/exctags/patches/patch-ab
--- a/devel/exctags/patches/patch-ab    Thu Jun 03 12:37:40 2004 +0000
+++ /dev/null   Thu Jan 01 00:00:00 1970 +0000
@@ -1,395 +0,0 @@
-$NetBSD: patch-ab,v 1.6 2003/04/07 09:30:43 seb Exp $
-
---- ctags.1.orig       2003-04-01 05:02:33.000000000 +0000
-+++ ctags.1
-@@ -1,27 +1,27 @@
--.TH CTAGS 1 "Version 5.5" "Darren Hiebert"
-+.TH EXCTAGS 1 "Version 5.5" "Darren Hiebert"
- 
- 
- .SH "NAME"
--ctags \- Generate tag files for source code
-+exctags \- Generate tag files for source code
- 
- 
- .SH SYNOPSIS
- .TP 6
--\fBctags\fP [\fBoptions\fP] [\fIfile(s)\fP]
-+\fBexctags\fP [\fBoptions\fP] [\fIfile(s)\fP]
- .TP 6
--\fBetags\fP [\fBoptions\fP] [\fIfile(s)\fP]
-+\fBexetags\fP [\fBoptions\fP] [\fIfile(s)\fP]
- 
- 
- .SH "DESCRIPTION"
--The \fBctags\fP and \fBetags\fP programs (hereinafter collectively referred to
--as \fBctags\fP, except where distinguished) generate an index (or "tag") file
-+The \fBexctags\fP and \fBexetags\fP programs (hereinafter collectively referred to
-+as \fBexctags\fP, except where distinguished) generate an index (or "tag") file
- for a variety of language objects found in \fIfile(s)\fP.
- This tag file allows these items to be quickly and easily located by a text
- editor or other utility. A "tag" signifies a language object for which an
- index entry is available (or, alternatively, the index entry created for that
- object).
- 
--Alternatively, \fBctags\fP can generate a cross reference file which lists, in
-+Alternatively, \fBexctags\fP can generate a cross reference file which lists, in
- human readable form, information about the various source objects found in a
- set of language files.
- 
-@@ -62,8 +62,8 @@ to a language and the file is executable
- checked to see if the file is a "#!" script for a recognized language.
- 
- By default, all other files names are ignored. This permits running
--\fBctags\fP on all files in either a single directory (e.g. "ctags *"), or on
--all files in an entire source directory tree (e.g. "ctags -R"), since only
-+\fBexctags\fP on all files in either a single directory (e.g. "exctags *"), or on
-+all files in an entire source directory tree (e.g. "exctags -R"), since only
- those files whose names are mapped to languages will be scanned.
- 
- [The reason that .h extensions are mapped to C++ files rather than C files
-@@ -73,8 +73,8 @@ treating them as C++ files.]
- 
- .SH "OPTIONS"
- 
--Despite the wealth of available options, defaults are set so that \fBctags\fP
--is most commonly executed without any options (e.g. "ctags *", or "ctags -R"),
-+Despite the wealth of available options, defaults are set so that \fBexctags\fP
-+is most commonly executed without any options (e.g. "exctags *", or "exctags -R"),
- which will create a tag file in the current directory for all recognized
- source files. The options described below are provided merely to allow custom
- tailoring to meet special needs.
-@@ -111,7 +111,7 @@ Use backward searching patterns (e.g. ?p
- .TP 5
- .B \-e
- Enable etags mode, which will create a tag file for use with the Emacs editor.
--Alternatively, if \fBctags\fP is invoked by a name containing the string
-+Alternatively, if \fBexctags\fP is invoked by a name containing the string
- "etags" (either by renaming, or creating a link to, the executable), etags
- mode will be enabled. This option must appear before the first file name.
- 
-@@ -122,7 +122,7 @@ or "TAGS" when running in etags mode). I
- "-", then the tag file is written to standard output instead. \fBCtags\fP
- will stubbornly refuse to take orders if \fItagfile\fP exists and its first
- line contains something other than a valid tags line. This will save your neck
--if you mistakenly type "ctags -f *.c", which would otherwise overwrite your
-+if you mistakenly type "exctags -f *.c", which would otherwise overwrite your
- first C file with the tags generated by the rest! It will also refuse to
- accept a multi character file name which begins with a '-' (dash) character,
- since this most likely means that you left out the tag file name and this
-@@ -163,7 +163,7 @@ Specifies a list of tokens which are to 
- and C++ source files. This option is specifically provided to handle special
- cases arising through the use of preprocessor macros. When the tokens listed
- are simple tokens, these tokens will be ignored during parsing of the source
--files. If a token is suffixed with a '+' character, \fBctags\fP will also
-+files. If a token is suffixed with a '+' character, \fBexctags\fP will also
- ignore any parenthesis-enclosed argument list which may immediately follow the
- token in the source files. If two tokens are separated with the '=' character,
- the first token is replaced by the second token for parsing purposes. The list
-@@ -273,9 +273,9 @@ includes: the tag name; the kind of tag;
- source line (with extra white space condensed) of the file which defines the
- tag. No tag file is written and all options affecting tag file output will be
- ignored. Example applications for this feature are generating a listing of all
--functions located in a source file (e.g. \fBctags -x --c-kinds\fP=\fIf\fP
-+functions located in a source file (e.g. \fBexctags -x --c-kinds\fP=\fIf\fP
- \fIfile\fP), or generating a list of all externally visible global variables
--located in a source file (e.g. \fBctags -x --c-kinds\fP=\fIv\fP
-+located in a source file (e.g. \fBexctags -x --c-kinds\fP=\fIv\fP
- \fB--file-scope\fP=\fIno file\fP). This option must appear before the first
- file name.
- 
-@@ -295,14 +295,14 @@ tag file which "includes" other tag file
- \fB--exclude\fP=[\fIpattern\fP]
- Add \fIpattern\fP to a list of excluded files and directories. This option
- may be specified as many times as desired. For each file name considered by
--\fBctags\fP, each \fIpattern\fP specified using this option will be compared
-+\fBexctags\fP, each \fIpattern\fP specified using this option will be compared
- against both the complete path (e.g. some/path/base.ext) and the base name
- (e.g. base.ext) of the file, thus allowing patterns which match a given file
- name irrespective of its path, or match only a specific path. If appropriate
- support is available from the runtime library of your C compiler, then
- \fIpattern\fP may contain the usual shell wildcards (not regular expressions)
- common on Unix (be sure to quote the option parameter to protect the wildcards
--from being expanded by the shell before being passed to \fBctags\fP; also be
-+from being expanded by the shell before being passed to \fBexctags\fP; also be
- aware that wildcards can match the slash character, '/'). You can determine if
- shell wildcards are available on your platform by examining the output of the
- \fB--version\fP option, which will include "+wildcards" in the compiled
-@@ -471,7 +471,7 @@ is enabled by default.
- 
- .TP 5
- \fB--filter\fP[=\fIyes\fP|\fIno\fP]
--Causes \fBctags\fP to behave as a filter, reading source file names from
-+Causes \fBexctags\fP to behave as a filter, reading source file names from
- standard input and printing their tags to standard output on a file-by-file
- basis. If \fB--sorted\fP is enabled, tags are sorted only within the source
- file in which they are defined. File names are read from standard output in
-@@ -485,7 +485,7 @@ by default. This option must appear befo
- \fB--filter-terminator\fP=\fIstring\fP
- Specifies a string to print to standard output following the tags for each
- file name parsed when the \fB--filter\fP option is enabled. This may permit an
--application reading the output of ctags to determine when the output for each
-+application reading the output of exctags to determine when the output for each
- file is finished. Note that if the file name read is a directory and
- \fB--recurse\fP is enabled, this string will be printed only one once at the
- end of all tags found for by descending the directory. This string will always
-@@ -557,7 +557,7 @@ enclosing the pattern in parentheses (e.
- support is available from the runtime library of your C compiler, then the
- file name pattern may contain the usual shell wildcards common on Unix (be
- sure to quote the option parameter to protect the wildcards from being
--expanded by the shell before being passed to \fBctags\fP). You can determine
-+expanded by the shell before being passed to \fBexctags\fP). You can determine
- if shell wildcards are available on your platform by examining the output of
- the \fB--version\fP option, which will include "+wildcards" in the compiled
- feature list; otherwise, the file name patterns are matched against file names
-@@ -584,7 +584,7 @@ file name patterns when inferring the la
- 
- .TP 5
- \fB--language-force\fP=\fIlanguage\fP
--By default, \fBctags\fP automatically selects the language of a source file,
-+By default, \fBexctags\fP automatically selects the language of a source file,
- ignoring those files whose language cannot be determined (see
- \fBSOURCE FILES\fP, above). This option forces the specified \fIlanguage\fP
- (case-insensitive; either built-in or user-defined) to be used for every
-@@ -622,7 +622,7 @@ Prints a summary of the software license
- Specifies whether "#line" directives should be recognized. These are present
- in the output of preprocessors and contain the line number, and possibly the
- file name, of the original source file(s) from which the preprocessor output
--file was generated. When enabled, this option will cause \fBctags\fP to
-+file was generated. When enabled, this option will cause \fBexctags\fP to
- generate tag entries marked with the file names and line numbers of their