Sean Reifschneider <jafo-python-dev@tummy.com> writes: > For test releases, I've been using the full release name as the extension, > /usr/bin/python2.2c1 (or was it just python2.2?). This is so that multiple > versions can be installed 1.5.2, 2.1, 2.2c1... That doesn't really work, does it? 2.2c1 would overwrite /usr/lib/python2.2, which might be there from a prior Python 2.2 installation. If it is just python2.2, that scheme would work. > Also, any other comments on the RPMs? Ideally, there should be an easy way to either install your RPMs alongside with the system RPMs, or to replace the system RPMs. In the latter case, 'rpm -U' could be used to upgrade from the system Python to your binaries. This might be tricky, as the names and structures of the Python RPMs vary widely. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4