Thread: [Vnc2swf-users] Packaging pyvnc2swf
Status: Alpha
Brought to you by:
euske
From: David F. <da...@sj...> - 2006-07-06 12:13:10
|
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/) It makes life much easier if pyvnc2swf files are installed in a package rather than just standalone, so to run this you need to move all the py files to a pyvnc2swf directory under the main source directory. This kind of move is of course annoying when using CVS, but I have found it makes projects much easier to package and distribute. I have made some source packages and builds using this system and placed them at http://davidf.sjsoft.com/files/pyvnc2swf/ pyvnc2swf-0.8.2.tar.gz - source tarball pyvnc2swf-0.8.2.tar.gz - source zip file pyvnc2swf-0.8.2-py2.4.egg - Python egg (from setuptools) pyvnc2swf-0.8.2-1.noarch.rpm - RPM for Python 2.4 pyvnc2swf-0.8.2-1.src.rpm - Source RPM pyvnc2swf-0.8.2.win32.exe - installer for installing Python package under Windows pyvnc2swf-0.8.2-setup.exe - standalone installer for installing py2exe package under Windows (includes Python libraries and all dependencies, doesn't require Python) The setup.py file is included below (it will only work with the rearranged source code of course, this is just for reference) Yusuke, if you don't have much time for this at the moment, would it be possible to get commit rights to the CVS repository? Or just briefly comment what you think about this? That would be appreciated Any comments from anyone else appreciated too... Regards David #!/usr/bin/env python from setuptools import setup, find_packages from distutils.cmd import Command try: import py2exe except ImportError: py2exe = None from pyvnc2swf import __version__ py2exe_options = {"dist_dir": "pyvnc2swf-%s-py2exe" % __version__.ver} setup( name = "pyvnc2swf", version = __version__.ver, packages = find_packages(), scripts = ["vnc2swf", "vnc2swf-edit", "vnc2swf-play"], package_data = {'': ["*.txt", "*.html"]}, # install_requires = ["pygame>=1.6", "pymedia>=1.3.5"], options = {"py2exe": py2exe_options, "build_installer": py2exe_options}, console = ["vnc2swf", "vnc2swf-edit", "vnc2swf-play"], entry_points = {"distutils.commands": ["build_installer = pyvnc2swf.innosetup:build_installer"]}, author = "Yusuke Shinyama", author_email = "yu...@cs...", maintainer = "David Fraser", maintainer_email = "da...@sj...", license = "GNU General Public License (GPL)", keywords = "vnc screencast movie record", url = "http://www.unixuser.org/~euske/vnc2swf/pyvnc2swf.html", download_url = "http://www.unixuser.org/~euske/vnc2swf/", description = "Pyvnc2swf is a cross-platform screen recording tool", long_description = "Pyvnc2swf is a cross-platform screen recording tool. It captures screen motion through VNC protocol and generates a Shockwave Flash (SWF) movie.", classifiers = [ "Development Status :: 4 - Beta", "Environment :: Console", "Environment :: Win32 (MS Windows)", "Environment :: X11 Applications", "Intended Audience :: End Users/Desktop", "License :: OSI Approved :: GNU General Public License (GPL)", "Natural Language :: English", "Operating System :: OS Independent", "Programming Language :: Python", "Topic :: Multimedia :: Video :: Capture", ], ) |
From: Yusuke S. <yu...@cs...> - 2006-10-29 20:16:08
|
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 |
From: David F. <da...@sj...> - 2006-10-30 09:17:39
|
Yusuke Shinyama wrote: > 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. > Thanks so much Yusuke, your efforts in py2vnc are certainly greater than mine! > 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. > Yes I know it can be a fair amount to test, but if its not just developers using the code, its even more work for them to get it running... Since I'm not likely to understand the core code any better than you, but have done a few fixes and can test on Linux and Windows, I'd be happy to package it My sourceforge id is davidfraser Regards David |