Re: [Vnc2swf-users] Packaging pyvnc2swf

[Yusuke S. <yu...@cs...>]

Hi David,

Sorry, I haven't noticed this message sent to the list way before
(yes, I was very busy at that time). I know this is an outdated
reply, but let me answer because I really appreciate your efforts.

On Thu, 06 Jul 2006 14:09:53 +0200, David Fraser <da...@sj...> wrote:
> Hi
> 
> I have created a setup script for pyvnc2swf which allows packaging it in
> any of the standard ways (source distribution, rpm, windows installer)
> and also as a py2exe standalone app on Windows.
> This uses the standard python distutils system, enhanced by setuptools
> (http://peak.telecommunity.com/DevCenter/setuptools) and py2exe
> (http://py2exe.sourceforge.net/)

This is great. I was planning this for long time and couldn't make
it, partly because I'm not familiar with Windows. But at the same
time I have concerns about the time we might have to spend for all
this packaging stuff. They're definitely convenient for end users,
but I'm afraid that it's taking so much time to prepare, because
even now, it's already becoming difficult to test all the possiblities
after adding a new function.

In fact, I don't like much of the idea of installing something on
my pc.  Instead, I just want to download a binary, double click it
to run, and throw away when it's unnecesary. This is the reason
why I didn't want to bring setup.py into the main pyvnc2swf
source. I'd like to separate the code development and its
distribution, otherwise sooner or later I will be unable to follow
its complexity by myself.  I'm simply afraid of this project
getting out of my hand.

That's said, if you're familiar with those stuff (looks like you
are) and willing to take care of them, I'm happy to get you cvs commit
rights. Please let me know your sourceforge id.

Thanks,
Yusuke