Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python-support’

2009-04-15 Thread Josselin Mouette
Le mercredi 15 avril 2009 à 15:17 +0200, Piotr Ożarowski a écrit : > how about: > * moving all files to usr/share/pyshared (just like you do now) > * registering files basing on usr/share/pyshared content (ignore > old .public/.private files) I’m afraid this would lose some information on the su

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-15 Thread Ben Finney
Piotr Ożarowski writes: > [Ben Finney, 2009-04-15] > > Josselin earlier suggested that ‘dh_pysupport’ will still look in > > ‘usr/share/python-support/’ for modules. Should I expect it to work with > > just ‘dh_install ; dh_pysupport’ if I use the following install file: > > > > = > > writer

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python-support’

2009-04-15 Thread Josselin Mouette
Le mercredi 15 avril 2009 à 14:19 +0200, Piotr Ożarowski a écrit : > oh, you can't - dh_pysupport doesn't pick up files from /usr/share/pyshared > (Joss: could you add this path to movemodules?) It’s not that simple, since that would prevent dh_pysupport from being idempotent. I guess I could just

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-15 Thread Ben Finney
Adeodato Simó writes: > dh_install would have been the tool of choice for this task, except > that your destination directory is not a static string: it depends on > the output of some command. Because of this, it can’t be sensibly used > for this. (If pysupport looked in some directory which doe

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-15 Thread Ben Finney
Ben Finney writes: > Adeodato Simó writes: > > > In that case, just use debian//usr/lib... instead, and skip > > the dh_install step. > > That does work, thank you. I spoke too soon; ‘dh_pysupport’ fails to find the module. The install process now shows the following output: = # Manual

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-15 Thread Ben Finney
Adeodato Simó writes: > + Ben Finney (Wed, 15 Apr 2009 20:19:55 +1000): > > > * Copy the file from ‘writers/manpage.py’ into ‘usr/lib/$(shell > > pyversions -d)/site-packages/docutils/writers/.’. If I omit this step, > > there is no indication that the modules should be in the > > ‘docutil

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-15 Thread Ben Finney
Piotr Ożarowski writes: > [Ben Finney, 2009-04-15] > > The only way that I know of so far to get ‘dh_pysupport’ to find and > > install the module correctly is: > > > > * Copy the file from ‘writers/manpage.py’ into ‘usr/lib/$(shell > > pyversions -d)/site-packages/docutils/writers/.’. If I om

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-15 Thread Ben Finney
Josselin Mouette writes: > Le mercredi 15 avril 2009 à 08:01 +1000, Ben Finney a écrit : > > Because it's double-handling: in the ‘debian/rules’ file I specify > > copying the modules once, and then in ‘debian/foo.install’ I specify > > copying them again. I want to copy them to one location that

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python-support’

2009-04-15 Thread Josselin Mouette
Le mercredi 15 avril 2009 à 08:01 +1000, Ben Finney a écrit : > > If there is no upstream build system, you need to replace it, and > > the .install file looks like the simplest way to do it. I don’t > > understand why you’d want to drop it. > > Because it's double-handling: in the ‘debian/rules’

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-14 Thread Ben Finney
Josselin Mouette writes: > Le mardi 14 avril 2009 à 22:09 +1000, Ben Finney a écrit : > > Where should I put the upstream library files so that the above > > ‘docutils-writer-manpage.install’ is not needed and ‘dh_pysupport’ > > will get them automatically? I have not come up with any combination

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python-support’

2009-04-14 Thread Josselin Mouette
Le mardi 14 avril 2009 à 22:09 +1000, Ben Finney a écrit : > What about in this case, where there *is* no upstream build system for > these modules and the only supported install method is “copy the module > files where you want them”? > > Where should I put the upstream library files so that the

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-14 Thread Ben Finney
Josselin Mouette writes: > Le mardi 14 avril 2009 à 16:51 +1000, Ben Finney a écrit : > > = > > --- > > docutils-writer-manpage-0.1~svn.r5663/debian/docutils-writer-manpage.install > > +++ > > docutils-writer-manpage-0.1~svn.r5663/debian/docutils-writer-manpage.install > > @@ -1 +1 @@ > > -

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python-support’

2009-04-14 Thread Josselin Mouette
Le mardi 14 avril 2009 à 16:51 +1000, Ben Finney a écrit : > > Put them into /usr/lib/python*/site-packages, as documented in its > > manpage? > > Thanks. That's new since the version of ‘python-support’ currently in > ‘squeeze’. (The ‘dh_pysupport(1)’ manpage in version 0.8.7 still talks > about

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-13 Thread Ben Finney
Cyril Brulebois writes: > Ben Finney (14/04/2009): > > I'm not very familiar with using ‘python-support’, so I'm not clear > > what I need to change in these rules. Where do I need to install the > > library files for them to be properly discovered by ‘dh_pysupport’? > > Put them into /usr/lib/

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-13 Thread Ben Finney
Ben Finney writes: > Cyril Brulebois writes: > > Put them into /usr/lib/python*/site-packages, as documented in its > > manpage? > > What, though, is ‘python*’ here? Remember, this is specifically for a > module that (at present) has no build system upstream; the code is > “installed” by manual

Re: Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-13 Thread Ben Finney
Cyril Brulebois writes: > Ben Finney (14/04/2009): > > As per bug#523965 http://bugs.debian.org/523965>, I'm attempting > > to migrate the ‘docutils-manpage-writer’ package from using > > ‘python-central’ to using ‘python-support’. > > *-writer-manpage, actually. Yes, thanks for the correction

Migrating unmanaged Python library extension from ‘python-central’ to ‘python -support’

2009-04-13 Thread Ben Finney
Howdy all, As per bug#523965 http://bugs.debian.org/523965>, I'm attempting to migrate the ‘docutils-manpage-writer’ package from using ‘python-central’ to using ‘python-support’. The original source currently has no installation method or build system; I am working with the upstream author to re