On Tue, 2006-07-18 at 22:47 +0200, Loïc Minier wrote: > This is a followup for Debian bug <http://bugs.debian.org/338117>. > > Hi Joe, > > On Tue, Jan 31, 2006, Joe Wreschnig wrote: > > I've proposed a relevant solution on [EMAIL PROTECTED] that lets > > Python modules provide shlibs-like data to generate > > dependencies/conflicts at build-time. It could be used to force things > > built with pygtk 2.8 to conflict with 2.6 (and vice versa) -- in fact, > > that's my example case, since this broke python-gst. > > After re-reading the bug, I'm not sure how the solution you propose > would solve the issue: codegen generates code dynamically, and I don't > see how it would "gain conscience" that it is being used from within a > Debian build and hence should set some substvar. > > Do you have pointers to the solution you've proposed and how I would > use it?
The idea was to do it only semi-automatically, with the building package required to declare that it needed to have the "pydeps" from the other package. dh_python would then grab the dependency information from the desired package and push the substvar itself. Like shlibs deps, the maintainer of the package would be responsible for updating the pydeps file. http://lists.debian.org/debian-python/2006/01/msg00151.html contains the full patch to dh_python, though undoubtedly it will no longer apply. In the current Python climate I think pushing for this change is totally out of the question. -- Joe Wreschnig <[EMAIL PROTECTED]>
