Hmm... so are we going to build vte 3 times so that we can deliver 2 bindings? That seems a bit excessive.
In the case of vte it's actually quite easy to deliver 2 sets of Python bindings from the same spec file, and without introducing 2 new ones. The python bindings are in a separate subdir called python, so basically, you can do something like: %build ... set PYTHON to 2.6 ./configure ... cp -pr python python2.4 <update PYTHON settings in python2.4/ for python 2.4> make cd python2.4 make %install ... make install DESTDIR=... cd python2.4 make install DESTDIR=... You can (and should) still deliver the bindings in 2 separate packages. Laca On Wed, 2009-10-28 at 18:56 +0000, Ghee Teo wrote: > http://defect.opensolaris.org/bz/show_bug.cgi?id=12096 > virt-manager requires a vte python module for 2.4 as it is also > depends > on libvirt which is not ready yet to move onto 2.6 due to dependency > on > libxml2 for 2.6 as well as lack of QE within the short term. > > The fix here is to deliver 2 new packages: > o SUNWpython24-vte > o SUNWpython26-vte > > each of these contains the python binding for vte for 2.4 and 2.6. > > The changes made are: > - Stop delivering vtemodule.so from SUNWgnome-terminal > - Deliver /usr/lib/python2.4/vendor-packages/gtk-2.0/vtemodule.so > with > SUNWpython24-vte > - Deliver /usr/lib/python2.6/vendor-packages/gtk-2.0/vtemodule.so > with > SUNWpython26-vte > > The base-specs/vte.spec is shared by the above 3 spec files. > > -Ghee >
