About python-support
Hi all, while fixing a bug in pointless, after rebuilding the package, I noticed that all the python modules that come with the package, are, according to the lastest debhelper (5.0.13), moved under /usr/share/python-support/pointless/pointless/ instead of usr/lib/pythonX.Y/site-packages. I have two questions: 1) Is it correct that the path is /usr/share/python-support/pointless/pointless/? Shouldn't be /usr/share/python-support/pointless/? Is it a dh_python bug? 2) Should I insert code in ponstist to remove old modules under usr/lib/pythonX.Y/site-packages/ by previous installations? or those are correctly managed by update-python-modules? Thanks, Marco -- "I videogiochi non influenzano i bambini. Voglio dire, se Pac-Man avesse influenzato la nostra generazione, staremmo tutti saltando in sale scure, masticando pillole magiche e ascoltando musica elettronica ripetitiva." "Videogames do not influence kids. I mean, if Pac-Man influenced our generation, we were all jumping in dark rooms, chomping pills and listening to electronic repeating music." Kristian Wilson, Nintendo Inc. 1989 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About python-support
Le mercredi 11 janvier 2006 à 12:06 +0100, Marco Presi a écrit : >I have two questions: > >1) Is it correct that the path is >/usr/share/python-support/pointless/pointless/? Shouldn't be >/usr/share/python-support/pointless/? Is it a dh_python bug? This path is correct. /usr/share/python-support/pointless maps the root of the python directory for the "pointless" package, and the module is also named "pointless". You can check this is correct by looking at the installation: the files should be installed in /var/lib/python-support/python2.3/pointless (and not pointless/pointless). >2) Should I insert code in ponstist to remove old modules under > usr/lib/pythonX.Y/site-packages/ by previous installations? or > those are correctly managed by update-python-modules? This should be handled by the prerm of the previous package. Regards, -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
upgrade path for python packages
Regarding the recent discussions about packaging of Python package, what is the recommended practise to provide a smooth upgrade path during the migration. Suppose upstream (pure) python lib foobar is currently packages as: python-foobar (dummy package depending on python2.3-foobar) python2.3-foobar (installs modules in /usr/lib/python2.3/site-packages) python2.4-foobar (installs modules in /usr/lib/python2.4/site-packages) And we want to migrate to a single package called python-foobar, which installs python module in /usr/lib/site-python/ How do we ensure that packages depending on python2.X-foobar won't break when the new package is installed? Do the following dependencies do the job: Package: python-foobar Provides: python2.3-foobar, python2.4-foobar Conflicts: python2.3-foobar, python2.4-foobar Replaces: python2.3-foobar, python2.5-foobar Thanks for your answers, -- Alexandre Fayolle signature.asc Description: Digital signature
Re: upgrade path for python packages
On Wed, Jan 11, 2006 at 06:00:21PM +0100, Alexandre Fayolle wrote: | Regarding the recent discussions about packaging of Python package, what | is the recommended practise to provide a smooth upgrade path during the | migration. [snip important contextual information] | Do the following dependencies do the job: | | Package: python-foobar | Provides: python2.3-foobar, python2.4-foobar | Conflicts: python2.3-foobar, python2.4-foobar | Replaces: python2.3-foobar, python2.5-foobar I'm not a DD or an expert, but based on my understanding I believe this does it. HTH, -D -- "Piracy is not a technological issue. It's a behavior issue." --Steve Jobs www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: upgrade path for python packages
Le mercredi 11 janvier 2006 à 18:00 +0100, Alexandre Fayolle a écrit : > Suppose upstream (pure) python lib foobar is currently packages as: > > python-foobar (dummy package depending on python2.3-foobar) > python2.3-foobar (installs modules in /usr/lib/python2.3/site-packages) > python2.4-foobar (installs modules in /usr/lib/python2.4/site-packages) > > And we want to migrate to a single package called python-foobar, which > installs python module in /usr/lib/site-python/ It is simpler to use python-support to do this. Just make a single python-foobar with the modules for the default python version. dh_python will move them to /usr/share/python-support, and they will be made available for all installed python versions. > How do we ensure that packages depending on python2.X-foobar won't break > when the new package is installed? You have two options here: 1. Make the package depend on python2.3, python2.4 and provide python2.3-foobar, python2.4-foobar. 2. Modify the packages using it to depend on python-foobar (if they are using /usr/bin/python) or python2.3, python-foobar (if they are using /usr/bin/python2.3). Option 1 ties up the package to specific python versions. My preference goes to option 2, as it doesn't break upgrades, it's just a matter of rebuilding the packages using the module. Regards, -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: Ceci est une partie de message numériquement signée
