On dom, 2011-12-11 at 11:29 +0100, Hartmut Goebel wrote: > Hi, > > I propose changing the release plan as follows. Please let me know > what you think
Please update the roadmap on the wiki as well. > > Major point: 1.6 should be named 2.0, since we have API changes: +1 on the renumbering. I think it makes sense to alert people that there are big changes in the way it is used. > Features for 2.0 > - see above > - eliminate config.dat etc. OK. > - PyInstaller home should be "read only", this is: no files are > written there OK. > - binchache is going to $HOME/.... (already implemented, but need to > be changed) OK but please fix it as previously discussed (I don't recall al the details now). I'm specifically worried about this. > Features for 2.1 > - time-stamp (ans maybe checksum) based cache (at least for bincache) This is already implemented (see cacheDigest); bincache is *only* checksum based and that's the only way it can work. Makeing it time-stamp based is prone to too many bugs; for instance, say that you constantly switch between two different wxPython versions; they have different .pyd files with same names; the fact that one is newer and one is older is immaterial; if I switch version, PyInstaller must refresh the bincache dir no matter the timestamp since the files are different. > - find import in extension modules (this would allow some hooks to be > removed) What's your plan here? > - can be installed using setuptools/easy_install/pip I don't think we should change anything in PyInstaller itself to accommodate installation tools. It's the other way around -- it's installation tools that must work with different packages which are reasonably distributed. That said, I'm OK with evaluating what needs to be done to work with pip. > - infos about how to package as an rpm (ReadMe-Pacakgingg.txt) This is something that it is better left to the distros, since each distro will have different requirements. Again, we must provide a reasonable application (read-only source directory, UNIX-friendly paths,e tc.), but the rest is up to them. > - idea, internal: use Python zlib instead of own copy We can't because we need to access zlib before python itself is loaded. I would evaluate using a more modern compression library instead (eg: xz) with higher compression ratios, assuming decompression speed is not impacted too much. > Features 3.0 (currently "2.0") > - Cover the distribution phase of installation: build an installer > wizard on Windows (through InnoSetup/NSIS), a DEB/RPM for Linux and a > DMG for Mac. I've *all* the code ready for InnoSetup, DEB, RPM and DMG, tested and used in production. Obviously it has been tested only on 2-3 different projects, so it might require some further refinements, but it would be a great start. I'm working on legal issues because I can't release it right now. When there is progress here, I'll let you know. -- Giovanni Bajo :: Develer S.r.l. [email protected] :: http://www.develer.com Blog: http://giovanni.bajo.it Last post: The algorithms behind OTP tokens -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
