Re: pkg/45345 (lang/python31 wrongly builds pyexpat)

[David Holland <dholland-pbugs%netbsd.org@localhost>]

The following reply was made to PR pkg/45345; it has been noted by GNATS.

From: David Holland <dholland-pbugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/45345 (lang/python31 wrongly builds pyexpat)
Date: Sun, 13 Nov 2011 22:19:36 +0000

 On Sun, Nov 13, 2011 at 09:40:04PM +0000, Joerg Sonnenberger wrote:
  > From: Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
  > To: gnats-bugs%NetBSD.org@localhost
  > Cc: 
  > Subject: Re: pkg/45345 (lang/python31 wrongly builds pyexpat)
  > Date: Sun, 13 Nov 2011 22:36:02 +0100
  > 
  >  On Sun, Nov 13, 2011 at 07:13:55PM +0000, dholland%NetBSD.org@localhost 
wrote:
  >  > State-Changed-Why:
  >  > That seems wrong.
  >  
  >  It isn't. It is the same situation with every other Python package and
  >  short of requiring all the dependencies on the main package, it is
  >  unlikely to get fixed.
 
 Eh?
 
 The base Python package should not depend on modules that are packaged
 separately. We explicitly yanked out the expat module (as well as a
 few others) to avoid having the base Python package depend on expat
 (as well as a few other things), which is generally a good thing.
 However, if we're going to do that we ought to do it fully or not at
 all. That is, anything in the base Python package that depends on
 modules we split out should itself be split out, or we should give up
 on trying to split some or all of these things out at all. Otherwise,
 things just break in bizarre ways, as per the previous mail.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost