Re: [pygtk] ANNOUNCE: PyGTK All-in-one Installer 2.22.6
yes, thank you On Thu, Jan 20, 2011 at 4:12 AM, John Stowers wrote: > On Wed, 2011-01-19 at 23:02 +0100, Tim Lebedkov wrote: >> Hello Dieter, >> >> I am really sorry. I have formulated my question so that you have >> completely misunderstood it. >> I hope that at least your explanations could be useful for somebody else. >> >> Let me explain my concerns in detail. In Npackd (package manager) I >> download packages from different >> locations like >> http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-1.win32-py2.7.msi >> To check that the download was OK, I compute the SHA1 checksum of the file. >> For this to work a file placed at a specific URL should never be changed. >> >> So here is my plea: don't overwrite files, but put new installers >> under a different URL and don't delete old installers. >> Examples: >> http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-1.win32-py2.7.msi >> http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-2.win32-py2.7.msi >> http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-3.win32-py2.7.msi > > Old installers are *never* deleted nor silently replaced on the GNOME > site. In fact that was the reason for the creation of the -1 variant; to > fix packaging bugs in windows, no PyGObject code was changed so we didnt > think it necessary to make a new PyGObject release with a version bump. > > I'm think Dieter misunderstood your question and offered an incorrect > reply. See below. > >> >> Thank You >> >> --Tim >> >> On Wed, Jan 19, 2011 at 10:01 PM, Dieter Verfaillie >> wrote: >> > On 19/01/2011 20:52, Tim Lebedkov wrote: >> >> am I right that files like >> >> http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-1.win32-py2.7.msi >> >> are just overwritten with a newer version of the installer? >> > >> > Correct. We do not (yet?) detect the presence of the separate pycairo, >> > pygobject, pygtk, pyrsvg, pygoocanvas and pygtksourceview2 packages. >> > Neither the .exe nor .msi installers. > > We don't detect if these have been *installed* on the users system. But > that is orthogonal to your questions (I think). If the all-in-one > installer requires new versions of the component installers then this > will be noted in the release notes and the README. > > As mentioned in the release notes, this installer only contains updated > gtk+ runtime, and updated glade installers. PyG* remain unchanged so no > installers were ever silently replaced on the GNOME servers. > > So in conclusion, if the all-in-one installer requires newer component > installer for any other PyG* packages, those component installers will > be uploaded to the GNOME servers with a new filename, and the README and > release notes of the all-in-one installer will make this clear. > > Hope that clears things up. > > John > > > >> This rather unfortunate behavior >> > is documented in the README [1] in the "Migrating from >> > PyGTK+PyGObject+PyCairo packages" section. >> > >> > I guess detecting the separate .exe installers could be done by checking >> > for either or both the "?-wininst.log"/"Remove?.exe" files in Python's >> > installation directory (this idea would need some serious testing though). >> > Detecting the separate .msi installers is a whole other matter: in this >> > case >> > distutils' bdist_msi command does not create the "?-wininst.log" or >> > "Remove?.exe" files. Detection by windows installer product codes might >> > work for known previous releases but we simply can't predict every >> > future release that's going to be created. That and maintaining such a >> > table of product codes would be a maintenance nightmare... >> > >> > Even if the aio installer would grow such a detection method, we cannot >> > provide the same for the inverse situation without seriously hacking >> > about with distutils' bdist_wininst and bdist_msi commands. So it is >> > equally possible to overwrite the aio installers' files by executing >> > on of the separate .exe or .msi installer... >> > >> >> Would it be possible to leave the old installers at their place and >> >> put the new under other names? >> > >> > Not really, the all-in-one installer repackages the content of the separate >> > .msi installers exactly as the
Re: [pygtk] ANNOUNCE: PyGTK All-in-one Installer 2.22.6
Hello Dieter, I am really sorry. I have formulated my question so that you have completely misunderstood it. I hope that at least your explanations could be useful for somebody else. Let me explain my concerns in detail. In Npackd (package manager) I download packages from different locations like http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-1.win32-py2.7.msi To check that the download was OK, I compute the SHA1 checksum of the file. For this to work a file placed at a specific URL should never be changed. So here is my plea: don't overwrite files, but put new installers under a different URL and don't delete old installers. Examples: http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-1.win32-py2.7.msi http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-2.win32-py2.7.msi http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-3.win32-py2.7.msi Thank You --Tim On Wed, Jan 19, 2011 at 10:01 PM, Dieter Verfaillie wrote: > On 19/01/2011 20:52, Tim Lebedkov wrote: >> am I right that files like >> http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-1.win32-py2.7.msi >> are just overwritten with a newer version of the installer? > > Correct. We do not (yet?) detect the presence of the separate pycairo, > pygobject, pygtk, pyrsvg, pygoocanvas and pygtksourceview2 packages. > Neither the .exe nor .msi installers. This rather unfortunate behavior > is documented in the README [1] in the "Migrating from > PyGTK+PyGObject+PyCairo packages" section. > > I guess detecting the separate .exe installers could be done by checking > for either or both the "?-wininst.log"/"Remove?.exe" files in Python's > installation directory (this idea would need some serious testing though). > Detecting the separate .msi installers is a whole other matter: in this case > distutils' bdist_msi command does not create the "?-wininst.log" or > "Remove?.exe" files. Detection by windows installer product codes might > work for known previous releases but we simply can't predict every > future release that's going to be created. That and maintaining such a > table of product codes would be a maintenance nightmare... > > Even if the aio installer would grow such a detection method, we cannot > provide the same for the inverse situation without seriously hacking > about with distutils' bdist_wininst and bdist_msi commands. So it is > equally possible to overwrite the aio installers' files by executing > on of the separate .exe or .msi installer... > >> Would it be possible to leave the old installers at their place and >> put the new under other names? > > Not really, the all-in-one installer repackages the content of the separate > .msi installers exactly as they are. That's the whole point of the aio > installer exercise, really (and was the tedious part to get right). > > To clarify things, both 2.22.5 and 2.22.6 include the following > extension modules (replace the ? with 6 or 7): > pycairo-1.8.10.win32-py2.?.msi > pygobject-2.26.0-1.win32-py2.?.msi > pygtk-2.22.0-1.win32-py2.?.msi > pygtksourceview-2.10.1.win32-py2.?.msi > pygoocanvas-0.14.2.win32-py2.?.msi > pyrsvg-2.32.1.win32-py2.6.msi > > It is however true that the -1 revision part of the version string > for pygtk and pygobject did not show in the "Custom Setup" page when > installing. I've fixed that in the build description file [2] and > the next version will be more clear about what package versions are > included in the UI. > > Regards, > Dieter > > [1] https://github.com/dieterv/pygtk-installer#readme > [2] > https://github.com/dieterv/pygtk-installer/blob/master/wix/2.22.7.win32.xml > ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
Re: [pygtk] ANNOUNCE: PyGTK All-in-one Installer 2.22.6
Hello Dieter, am I right that files like http://ftp.gnome.org/pub/GNOME/binaries/win32/pygobject/2.26/pygobject-2.26.0-1.win32-py2.7.msi are just overwritten with a newer version of the installer? Would it be possible to leave the old installers at their place and put the new under other names? --Tim On Wed, Jan 19, 2011 at 8:23 PM, Dieter Verfaillie wrote: > We are pleased to announce release 2.22.6 of the PyGTK All-in-one > installer for Windows. > > More information can be found in the README file at: > https://github.com/dieterv/pygtk-installer#readme > > * What is it? > = > > The PyGTK All-in-one installer provides an alternative installation > method for PyGTK users on Windows. It bundles PyGTK, PyGObject, > PyCairo, PyGtkSourceView2, PyGooCanvas, PyRsvg, the gtk+-bundle > and Glade in one handy installer. > > Currently 32 bit Python 2.6 and 2.7 versions are supported > on Windows XP and up. > > Some screenshots can be seen at: > https://github.com/dieterv/pygtk-installer/wiki > > * What's changed in 2.22.6 ? > > > * Updated bundled GTK+ runtime packages to > gtk+-bundle_2.22.1-20101227_win32 which fixes the svg pixbuf > loader issues described in > https://bugzilla.gnome.org/show_bug.cgi?id=637742. > * Grammatical fixes to the README and build_installer.py script > by David Ripton. > * Updated glade3-3.6.7 packages + the build_glade.sh script is now > tracked at https://bugzilla.gnome.org/show_bug.cgi?id=634978 > > The PyGTK, PyGObject, PyCairo, PyGtkSourceView2, PyGooCanvas and > PyRsvg extension modules remain unchanged. > > * Where to get it? > == > > binaries: > > http://download.gnome.org/binaries/win32/pygtk/2.22/pygtk-all-in-one-2.22.6.win32-py2.6.msi > md5sum : 1ce2abcaa4b232e52111a71e937f52e9 > size : 32,3M > > http://download.gnome.org/binaries/win32/pygtk/2.22/pygtk-all-in-one-2.22.6.win32-py2.7.msi > md5sum : 75cfe879a13ae99d5b19fee4f1597bb5 > size : 32,3M > > source code of the installer build tool: > > https://github.com/dieterv/pygtk-installer/tree/release-2.22.6 > https://github.com/dieterv/pygtk-installer/tarball/release-2.22.6 > https://github.com/dieterv/pygtk-installer/zipball/release-2.22.6 > > > Enjoy! > > The PyGTK Team > ___ > pygtk mailing list pygtk@daa.com.au > http://www.daa.com.au/mailman/listinfo/pygtk > Read the PyGTK FAQ: http://faq.pygtk.org/ > ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
[pygtk] Npackd (package manager for Windows) for PyGTK applications
Hello, as announced in September the new version of Npackd (http://code.google.com/p/windows-package-manager/) is ready and now also supports dependencies between packages. Thanks to the great work of Dieter Verfaillie (MSI packages) and the help of Alessandro Dentella all the dependencies necessary for a PyGTK application are already in-place (GTK+, PyGTK, PyGObject, PyCairo). If you want to use Npackd to distribute your PyGTK-application, it would be probably enough to zip your .py files and define the dependencies. There is a PyGTK application in the repository, if you want to try it out: GRAMPS. Regards --Tim ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
Re: [pygtk] ANNOUNCE: PyGTK All-in-one Installer 2.22.5
thank you. That's great! On Fri, Dec 24, 2010 at 10:05 AM, Dieter Verfaillie wrote: > On 24/12/2010 09:44, Tim Lebedkov wrote: >> thank you for the effort. I use the installers from >> http://www.optionexplicit.be/projects/gnome-windows/20101102/ in >> Npackd. Is it the right location? > > I keep everything on optionexplicit.be available as long as > possible, but sometimes I need to remove older files (due to > resource constraints). The good news is that all installers > from the 20101102 directory are are now also hosted on > http://download.gnome.org: > > PyGTK (as the pygtk-2.22.0-1 revision): > http://download.gnome.org/binaries/win32/pygtk/2.22/ > > PyGObject (as the pygobject-2.26.0-1 revision): > http://download.gnome.org/binaries/win32/pygobject/2.26/ > > PyCairo: > http://download.gnome.org/binaries/win32/pycairo/1.8/ > > PyGooCanvas: > http://download.gnome.org/binaries/win32/pygoocanvas/0.14/ > > PyGtkSourceView2: > http://download.gnome.org/binaries/win32/pygtksourceview/2.10/ > > PyRsvg: > http://download.gnome.org/binaries/win32/gnome-python-desktop/2.32/ > >> Will you still provide installers >> for single libraries? > > Yes. Be assured the separate installers are not going away, they > are even a requirement to build the all-in-one installer. > > mvg, > Dieter > ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
Re: [pygtk] ANNOUNCE: PyGTK All-in-one Installer 2.22.5
Hello Dieter, thank you for the effort. I use the installers from http://www.optionexplicit.be/projects/gnome-windows/20101102/ in Npackd. Is it the right location? Will you still provide installers for single libraries? --Tim On Fri, Dec 24, 2010 at 6:55 AM, Dieter Verfaillie wrote: > We are pleased to announce release 2.22.5 of the PyGTK All-in-one > installer for Windows. > > More information can be found in the README file at: > https://github.com/dieterv/pygtk-installer#readme > > * What is it? > = > The PyGTK All-in-one installer provides an alternative installation > method for PyGTK users on Windows. It bundles PyGTK, PyGObject, > PyCairo, PyGtkSourceView2, PyGooCanvas, PyRsvg, the gtk+-bundle > and Glade in one handy installer. > > Currently 32 bit Python 2.6 and 2.7 versions are supported > on Windows XP and up. > > Some screenshots can be seen at: > https://github.com/dieterv/pygtk-installer/wiki > > * Where to get it? > == > > binaries: > > http://download.gnome.org/binaries/win32/pygtk/2.22/pygtk-all-in-one-2.22.5.win32-py2.6.msi > md5sum : 3acbd0ef3c13c1112d6f119bdb076ac6 > size : 32,3M > > http://download.gnome.org/binaries/win32/pygtk/2.22/pygtk-all-in-one-2.22.5.win32-py2.7.msi > md5sum : 7a0272a0bd5c857b994f2eed92af199f > size : 32,3M (33091012) > > source code: > > https://github.com/dieterv/pygtk-installer/tree/release-2.22.5 > https://github.com/dieterv/pygtk-installer/tarball/release-2.22.5 > https://github.com/dieterv/pygtk-installer/zipball/release-2.22.5 > > > Enjoy! > > The PyGTK Team > ___ > pygtk mailing list pygtk@daa.com.au > http://www.daa.com.au/mailman/listinfo/pygtk > Read the PyGTK FAQ: http://faq.pygtk.org/ > ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
Re: [pygtk] Silent installation
Hello Dieter, it seems to be a rather difficult case so I would probably come back later after support for dependencies in my program is released. Thank you and all the others who answered. --Tim On Mon, Sep 20, 2010 at 8:00 AM, Dieter Verfaillie wrote: > Hi, > > Quoting "John Stowers" : >> >> On Sun, 2010-09-19 at 20:07 +0200, Tim Lebedkov wrote: >> The installers are generated by the python distutils machinery, so I am >> not sure if they support /S. > > I think the .msi installers generated by bdist_msi support a silent flag... > >> I suspect they could *almost* be expressed as a batch file and a ZIP >> download, as most of the work is copying files to the correct location. >> The one exception is the postinstall script which has to fix the >> pkg-config files to point to the install directory. > > ... but then there's no way to execute the postinstall script (that I'm > aware of) > > mvg, > Dieter > > > > This message was sent using IMP, the Internet Messaging Program. > > ___ > pygtk mailing list pygtk@daa.com.au > http://www.daa.com.au/mailman/listinfo/pygtk > Read the PyGTK FAQ: http://faq.pygtk.org/ > ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
Re: [pygtk] Silent installation
Hello John, do the installers support a command line parameter for silent installation? Something like /S? If no, is there a ZIP-download? What does the installer do? Can it be expressed in a batch file? Regards --Tim On Sun, Sep 19, 2010 at 11:57 AM, John Stowers wrote: > On Sun, 2010-09-19 at 09:28 +0430, Saeed Rasooli wrote: >> I think there is lake of a Package Manager (like apt-get) in windows >> to contoll complex dependency structure of libraries and their needing >> versions. Thats because fully installation of PyGTK (including python, >> python-gtk, libgtk, libcairo, lib* ...) was ALYAWS A PROBLEM. I >> usually use Linux, but every time I try to install PyGTK and many >> other GTK-based programs (like Pidgin and GIMP) inside windows, I find >> it too hard and I sense this structure is not built for windows. Qt is >> more successful in windows maybe because it collects everything in one >> place! > > Hi, > > I generate the PyGtk installers for windows. > > Every few months someone wishes for an all in one installer, but no one > ever includes any concrete suggestions for how one would be compiled, or > what exactly it would contain. > > So basically, if you are interested in an all in one installer for the > PyGtk stack on windows, make one as a prototype, we can then all test > it, then I will be happy to get it hosted on GNOME servers and maintain > it into the future. > > John > >> >> On Sat, Sep 18, 2010 at 10:22 PM, Tim Lebedkov >> wrote: >> Hello, >> >> is there a way to install PyGTK silently (without user >> interaction)? >> >> Regards >> --Tim >> ___ >> pygtk mailing list pygtk@daa.com.au >> http://www.daa.com.au/mailman/listinfo/pygtk >> Read the PyGTK FAQ: http://faq.pygtk.org/ >> >> ___ >> pygtk mailing list pygtk@daa.com.au >> http://www.daa.com.au/mailman/listinfo/pygtk >> Read the PyGTK FAQ: http://faq.pygtk.org/ > > > ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
Re: [pygtk] Silent installation
Hello Saeed, I actually try to write one. All the dependencies can be installed (see for example Pango: http://code.google.com/p/windows-package-manager/source/detail?r=156e02dda84782d83105c24756e3daa8707fa422). How can I install PyGTK now? Regards --Tim On Sun, Sep 19, 2010 at 6:58 AM, Saeed Rasooli wrote: > I think there is lake of a Package Manager (like apt-get) in windows to > contoll complex dependency structure of libraries and their needing > versions. Thats because fully installation of PyGTK (including python, > python-gtk, libgtk, libcairo, lib* ...) was ALYAWS A PROBLEM. I usually use > Linux, but every time I try to install PyGTK and many other GTK-based > programs (like Pidgin and GIMP) inside windows, I find it too hard and I > sense this structure is not built for windows. Qt is more successful in > windows maybe because it collects everything in one place! > > On Sat, Sep 18, 2010 at 10:22 PM, Tim Lebedkov > wrote: >> >> Hello, >> >> is there a way to install PyGTK silently (without user interaction)? >> >> Regards >> --Tim >> ___ >> pygtk mailing list pygtk@daa.com.au >> http://www.daa.com.au/mailman/listinfo/pygtk >> Read the PyGTK FAQ: http://faq.pygtk.org/ > > ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
[pygtk] Silent installation
Hello, is there a way to install PyGTK silently (without user interaction)? Regards --Tim ___ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
