Bug#338117: Bug#338090: Broken python binding

On Tue, 2006-07-18 at 22:47 +0200, Loïc Minier wrote: > This is a followup for Debian bug . > > 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-lik

Bug#338117: Bug#338090: Broken python binding

This is a followup for Debian bug . 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

Bug#338117: Bug#338090: Broken python binding

Hi Loïc, 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

Bug#338117: Bug#338090: Broken python binding

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) -