On Tue, Dec 23, 2008 at 10:48:41AM +0000, wrobell wrote: > On Fri, Dec 19, 2008 at 06:19:19PM +0000, wrobell wrote: > > On Fri, Dec 19, 2008 at 09:49:35AM +0100, matkor wrote: > > > Author: matkor Date: Fri Dec 19 08:49:34 2008 GMT > > > Module: SPECS Tag: HEAD > > > ---- Log message: > > > - Release 3. Killed nonworking mx bcond. Prepared for Ac. > > > > now, if somebody wants to to compile psycopg, then he has to build it with > > mx.DateTime, which > > - is non-standard > > - i don't know any modern application, which uses it > > > > what's the point? is it for python 2.4 and Ac? then just do that on ac > > branch, please. > > > > at least, you could leave mx bcond and explain why it is not working for > > you. > > no answer so far and my understanding is that matkor's change was due to > python 2.4 in ac. therefore my proposal to solve this conflict is as > follows > - i will move python-psycopg2.spec to AC-branch > - i will revert HEAD of the spec to previous version and upgrade it > to 2.0.8 > - if distro line bconds (whatever you call it) are allowed on HEAD, > then matkor, please use the distro line bcond instead of py_ver hack > (to not introduce more mess), but please leave mx bcond for those > who would like to use it[1]
i changed my mind. AC bcond is used. hope that's ok and it won't invoke any fucking cvs commit war. regards, wrobell <wrob...@pld-linux.org> _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en