On Monday 06 November 2006 08:18, Andreas Pakulat wrote:
On 05.11.06 19:20:00, Simon Edwards wrote:
I don't think that is quite the case. The standard approach that
distributions
use for this kind of problem is to make it possible to install the old
version along side the new one. This
On 06.11.06 21:01:59, Simon Edwards wrote:
On Monday 06 November 2006 08:18, Andreas Pakulat wrote:
On 05.11.06 19:20:00, Simon Edwards wrote:
This is no different than an upgrade of libstdc++ would work, if they
change their ABI or even API. You can't install 2 versions of that
either,
On Sunday 05 November 2006 00:29, Phil Thompson wrote:
On Saturday 04 November 2006 10:08 pm, Simon Edwards wrote:
sip.so. Point is, once a SIP wrapper for a custom C++ class is compiled it
then depends on that particular version of sip.
No it doesn't.
Are you trying to tell me that if I
On Sunday 05 November 2006 11:28 am, Simon Edwards wrote:
On Sunday 05 November 2006 00:29, Phil Thompson wrote:
On Saturday 04 November 2006 10:08 pm, Simon Edwards wrote:
sip.so. Point is, once a SIP wrapper for a custom C++ class is compiled
it then depends on that particular version
Andreas Pakulat wrote:
I think the most problematic part for getting PyQt as egg is
integrating the PyQt buildsystem (and sips probably too) into
the setuptools.
I have posted to this list an incomplete setup.py for building and installing
SIP. It was built atop of distutils, but it could be
On Sunday 05 November 2006 13:15, Phil Thompson wrote:
I understand where you are coming from, and the situation you describe is
perfectly possible - and no different from hundreds of other open source
packages.
I don't think that is quite the case. The standard approach that distributions
On 05.11.06 19:20:00, Simon Edwards wrote:
On Sunday 05 November 2006 13:15, Phil Thompson wrote:
I understand where you are coming from, and the situation you describe is
perfectly possible - and no different from hundreds of other open source
packages.
I don't think that is quite the
On Saturday 04 November 2006 7:47 pm, Simon Edwards wrote:
Hello,
One of the things that I would like to see in PyKDE 4 is the possibility to
install different versions PyQt into the same Python installation in the
event that backward compatibility in libsip needs to be broken.
Anyway, I've
On Saturday 04 November 2006 21:38, Phil Thompson wrote:
On Saturday 04 November 2006 7:47 pm, Simon Edwards wrote:
This would be very useful for PyKDE and KDE 4. Phil, what do you think?
Yuck. So, in the hypothetical case where a binary incompatibility is
introduced you then go through all
On Saturday 04 November 2006 10:08 pm, Simon Edwards wrote:
On Saturday 04 November 2006 21:38, Phil Thompson wrote:
On Saturday 04 November 2006 7:47 pm, Simon Edwards wrote:
This would be very useful for PyKDE and KDE 4. Phil, what do you think?
Yuck. So, in the hypothetical case where
On 04.11.06 23:29:08, Phil Thompson wrote:
On Saturday 04 November 2006 10:08 pm, Simon Edwards wrote:
On Saturday 04 November 2006 21:38, Phil Thompson wrote:
If you want module version dependencies then don't eggs give you what you
need?
From what little I just read about python
11 matches
Mail list logo
