On Sun, 12 Nov 2006, Yusuke Shinyama wrote:
> On Sun, 12 Nov 2006 16:13:35 +0100 (CET), Dag Wieers <da...@wi...> wrote:
>
> > It would be really useful if the website would mention what version of
> > python you need for every release. I currently am looking what version of
> > pyvnc2swf would still work for the following python versions:
> >
> > python 2.3.4 EL4, FC3
> > python 2.3.3 FC2
> > python 2.2.3 EL3, FC1
> > python 2.2.2 RH9
> >
> > The need for this is that I'm packaging bith vnc2swf and now pyvnc2swf and
> > the latest version does not work for anything older than python 2.4. But
> > that makes pyvnc2swf not a solution for anything other than FC5 and FC6.
> >
> > You can find vnc2swf packages for Red Hat Enterprise Linux and Fedora Core
> > at:
> >
> > http://dag.wieers.com/packages/vnc2swf/
> > http://dag.wieers.com/packages/pyvnc2swf/
> >
> > You may also be interested in how the packaging has been done for
> > pyvnc2swf since there is no installation guideline or best-practices for
> > something like this we opted to move everything to /usr/share/pyvnc2swf/
> > and make 3 script (pyvnc2swf, pyvnc2swf-edit and pyvnc2swf-play) much like
> > altlinux is currently doing.
> >
> > It's generally accepted that the author should provide a standard way of
> > installation so that packagers do it alike (instead how they feel) :)
>
> I'm going to release a new version which is free from 2.4-specific syntax.
> Hopefully it works on Python 2.3 too...
That would be better than I had hoped for. I had hoped an earlier release
would have worked on something older than 2.4.
> Porting this to Python 2.2 is not easy, as it lacks one of the necessary
> socket APIs (socket.settimeout).
I understand. With python there is always a balance between supporting
current distributions and the need/ease to use the newer python
infrastructure.
Kind regards,
-- dag wieers, da...@wi..., http://dag.wieers.com/ --
[all I want is a warm bed and a kind word and unlimited power]
|
