On Mon, Feb 18, 2002 at 12:33:55PM +0100, Christian Kurz wrote: > On 17/02/02, Matt Zimmerman wrote: > > and this one package with one set of install/remove scripts supports > > emacs20, emacs21, xemacs21. When a new emacs is installed, the > > installed elisp packages are byte-compiled for it, and when one is > > removed, the byte-compiled files are removed. These packages don't have > > to build-depend on any emacs, much less multiple versions (as with these > > python packages). > > Well, but why can't you then use one generic install and remove script and > pass it not only the version number but also the package name and let it > then handle the byte-compiling? It would remove the need to add mostly > identical scripts to the packages and therefor make it easier to maintain > the packages.
Good plan; why not do that for python? How about a /usr/sbin/python-pkgtool --install <package> /usr/sbin/python-pkgtool --remove <package> Which will have knowledge of which python versions are installed, and byte-compile/purge the appropriate files. That way, the logic about which versions are installed, and the details of byte compilation, stay out of module package maintainer scripts. One detail that needs to be handled is to only make the package available for the python versions that it works with. I don't like having multiple packages; for pure python modules the code often seems to work with multiple versions of python. -- - mdz
