Hmm,

I had a swig-build installed before, then deleted the old p5-subversion
and tried to build the new one.
At that stage the new p5-subversion wanted the new swig13 package and installed it:

===> Registering installation for swig-1.3.24
pkg_create: Overwriting /usr/pkg/bin/swig - pkg swig-build-1.3.19 bogus/conflicting?

If this package should really replace the old ones then it needs
a CONFLICTS line, like this one:

CONFLICTS= swig-build-*

And maybe for the other modules too, because they have no DEPENDS line for swig-build
and would stay around even if you delete swig-build.

Bernd

On Mon, May 23, 2005 at 10:25:03PM +0000, Eric Gillespie wrote:
> 
> Module Name:	pkgsrc
> Committed By:	epg
> Date:		Mon May 23 22:25:03 UTC 2005
> 
> Update of /cvsroot/pkgsrc/devel/swig13
> In directory ivanova.netbsd.org:/tmp/cvs-serv5595
> 
> Log Message:
> Import SWIG-1.3.24.
> 
> Originally, this was going to be a meta-package for
> swig-{build,python,perl,...}, but SWIG no longer has run-time
> components, and may now be collapsed into a single package.
> 
> SWIG (Simplified Wrapper and Interface Generator)
> 
> SWIG is a compiler that integrates C and C++ with languages including
> Perl, Python, Tcl, Guile, Mzscheme, Java, Ruby, PHP, and Ocaml.
> 
> SWIG reads annotated C/C++ header files and creates wrapper code (glue
> code) in order to make the corresponding C/C++ libraries available to
> the listed languages, or to extend C/C++ programs with a scripting
> language.
> 
> Status:
> 
> Vendor Tag:	TNF
> Release Tags:	pkgsrc-base
> 		
> N pkgsrc/devel/swig13/Makefile
> N pkgsrc/devel/swig13/distinfo
> N pkgsrc/devel/swig13/PLIST
> N pkgsrc/devel/swig13/DESCR
> N pkgsrc/devel/swig13/buildlink3.mk
> N pkgsrc/devel/swig13/patches/patch-aa
> 
> No conflicts created by this import
>