-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Every time I see a change like this, I'm worried that it makes
building binary packages next to impossible. Does the package
name change when XANIM_CODECS is set differently?  If not, how
does one choose which binary package to install?

- --Michael

"Johnny C. Lam" <jlam@netbsd.org> writes:

> Module Name:	pkgsrc
> Committed By:	jlam
> Date:		Wed Sep 25 12:04:07 UTC 2002
> 
> Modified Files:
> 	pkgsrc/graphics/xanim: Makefile distinfo
> 	pkgsrc/graphics/xanim/patches: patch-ab patch-ae
> Added Files:
> 	pkgsrc/graphics/xanim: Makefile.codecs
> 
> Log Message:
> Create a new variable XANIM_CODECS, whose value is a space-separated list
> of codecs that may be compiled into xanim: iv32, cvid, and cyuk.  The
> default is to compile them all into xanim.  This allows building a xanim
> that may be distributed on CD-ROM by removing the restricted codecs from
> the XANIM_CODECS list (currently, this is iv32 and cyuk).  For clarity,
> separate the codec-handling into a separate Makefile.codecs.
> 
> 
> To generate a diff of this commit:
> cvs rdiff -r1.27 -r1.28 pkgsrc/graphics/xanim/Makefile
> cvs rdiff -r0 -r1.1 pkgsrc/graphics/xanim/Makefile.codecs
> cvs rdiff -r1.7 -r1.8 pkgsrc/graphics/xanim/distinfo
> cvs rdiff -r1.10 -r1.11 pkgsrc/graphics/xanim/patches/patch-ab
> cvs rdiff -r1.2 -r1.3 pkgsrc/graphics/xanim/patches/patch-ae
> 
> Please note that diffs are not public domain; they are subject to the
> copyright notices on the relevant files.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (NetBSD)
Comment: See http://www.flame.org/~explorer/pgp for my keys

iD8DBQE9tbl+l6Nz7kJWYWYRAvNiAJ4mkVOPcNBEJ8ZYqghxu/ItzG1PLACdH5G5
bCVhvQAVe/nhB0+lTXGILAY=
=9T7U
-----END PGP SIGNATURE-----