[Greg Troxel] CVS commit: pkgsrc/devel/py-darcsver

[Greg Troxel <gdt%ir.bbn.com@localhost>]

Joerg pointed out to me that py-cryptopp seemed to need py-expat.  I
think that's because it runs py-darcsver stuff at install time and that
does an import of py-expat things.  So the below should fix that.

But, I wonder if the bl3 framework could be extended to have support for
perl and python (and ruby and .....), so that interpreted running during
packaging would have a restricted view and only see things that had been
bl3'd in, just like regular libraries.

I realize there's perhaps some tension between turning bl3 into a
virtual bulkd build environment, because having a chroot that only has
the required packages installed is what bl3 spiffage will asymptotically
appraoch.

--- Begin Message ---

• To: pkgsrc-changes%NetBSD.org@localhost
• Subject: CVS commit: pkgsrc/devel/py-darcsver
• From: Greg Troxel <gdt%netbsd.org@localhost>
• Date: Sun, 26 Sep 2010 13:53:47 +0000

Module Name:    pkgsrc
Committed By:   gdt
Date:           Sun Sep 26 13:53:47 UTC 2010

Modified Files:
        pkgsrc/devel/py-darcsver: Makefile

Log Message:
Express dependency on py-expat.

(The python world seems to think that xml parsing functions are part
of core Python and need not be mentioned.  Perhaps pkgsrc's way of
having py-expat is unusual and a bit of DESCR spiffage is in order,
but I'm not sure what's right.)


To generate a diff of this commit:
cvs rdiff -u -r1.1.1.1 -r1.2 pkgsrc/devel/py-darcsver/Makefile

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

--- End Message ---