Am 11.12.2011 14:42, schrieb Giovanni Bajo:
Please update the roadmap on the wiki as well.
Done.
- 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.
This is documented in http://www.pyinstaller.org/ticket/307. We may need
to finish this discussion prior to implementing.
Features for 2.1
- time-stamp (ans maybe checksum) based cache (at least for bincache)
This is already implemented (see cacheDigest); bincache is *only*
Oh, I did not know. This is even better then :-) My central idea was
using this for bincahce and expire the entries there. This is more
related to #307.
- find import in extension modules (this would allow some hooks to be
removed)
What's your plan here?
It's just an idea yet, Martin had (http://www.pyinstaller.org/ticket/438).
- 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.
People are used to install using pip or easy_install. So this will
increase the userbase. There is not much to do beside writing a proper
setup.py as we already moved to a `PyInstaller` library-package.
- 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.
Same reason as above: Increase user base. A Readme eases the work for
the packagers since they get informations where are the places (or at
least some of them) they need to look at. E.g. patching pathes in
`PyInstaller/__init__.py` It's a service from us developers :-)
- 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.
Sorry, I meant libz.so, not the python module zlib.
Using an enhances algo is another good idea.
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
Wow!
--
Schönen Gruß - Regards
Hartmut Goebel
Dipl.-Informatiker (univ.), CISSP, CSSLP
Goebel Consult
Spezialist für IT-Sicherheit in komplexen Umgebungen
http://www.goebel-consult.de
Monatliche Kolumne: http://www.cissp-gefluester.de/
Goebel Consult ist Mitglied bei http://www.7-it.de
--
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.
