Request for help to convert the lyx package

Hello,
I've been working on the lyx package to get it in a state
complying with
the new python policy.

LyX generates some .pyc and .pyo files during build time and
I'm not
sure what to do with them because I thought that the
dh_pycentral call
would handle them correctly. Having build a package[1] from
the stuff we
currently have in our svn repo[2] I can not find a
postinst/prerm script
added to handle the recompilation of those files.
>From the resulting packages lyx-common is the one with
the python stuff.

I'd appreciate if someone could enlight me and tell me how
to deal with
this case correctly.

Regards,
Sven

[1] http://sven.sto
rmbind.net/debian/lyx/
[2] http://svn.debian.org/wsvn/pkg-lyx/lyx/trunk/?rev=0&
amp;sc=0


-- 
If you won't forgive me the rest of my life
Let me apologize while I'm still alive
I know it's time to face all of my past mistakes
  [Less than Jake - Rest Of My Life]


-- 
To UNSUBSCRIBE, email to debian-python-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble?
Contact listmasterlists.debian.org

Le mer 2 août 2006 12:37, Sven Hoexter a écrit :
> Hello,
> I've been working on the lyx package to get it in a
state complying
> with the new python policy.
>
> LyX generates some .pyc and .pyo files during build
time and I'm not
> sure what to do with them because I thought that the
dh_pycentral
> call would handle them correctly. Having build a
package[1] from the
> stuff we currently have in our svn repo[2] I can not
find a
> postinst/prerm script added to handle the recompilation
of those
> files.
>
> >From the resulting packages lyx-common is the one
with the python
> > stuff.
>
> I'd appreciate if someone could enlight me and tell me
how to deal
> with this case correctly.

first you need to build depends on python-dev and not
python.

and the pyo and pyc files are generated by your build
process. you have 
to remove them manually, e.g. using some find -name
'*.pyo' mantra.

there should be no .pyo/.pyc in the packages you build,
those are 
created by pycentral at postinst / prerm time of your
package, thanks 
to debhelper magic.
-- 
·O·  Pierre Habouzit
··O                                               
madcoderdebian.org
OOO                                                http://www.madism.org

On Wed, Aug 02, 2006 at 07:42:40PM +0200, Pierre Habouzit
wrote:
 
> and the pyo and pyc files are generated by your build
process. you have 
> to remove them manually, e.g. using some find -name
'*.pyo' mantra.

The (old) dh_python did remove the .pyc and .pyo files at
package build
time, so one did not have to bother with their removal. Are
the new
fancy tools not doing this (asks a developer still not
up-to-date with
the new python policy)?

Thanks,
Iustin Pop


-- 
To UNSUBSCRIBE, email to debian-python-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble?
Contact listmasterlists.debian.org

Le mer 2 août 2006 19:51, Iustin Pop a écrit :
> On Wed, Aug 02, 2006 at 07:42:40PM +0200, Pierre
Habouzit wrote:
> > and the pyo and pyc files are generated by your
build process. you
> > have to remove them manually, e.g. using some find
-name '*.pyo'
> > mantra.
>
> The (old) dh_python did remove the .pyc and .pyo files
at package
> build time, so one did not have to bother with their
removal. Are the
> new fancy tools not doing this (asks a developer still
not up-to-date
> with the new python policy)?

looking at dh_python source, bumping PYCOMPAT to 2 does not
changes that 
part of its behaviour.

though, even for the lyx-common in the archive there is
.pyo/.pyc 
in /usr/share/lyx/lyx2lyx/ (wich in itself is quite bad).

-- 
·O·  Pierre Habouzit
··O                                               
madcoderdebian.org
OOO                                                http://www.madism.org

On Wed, Aug 02, 2006 at 08:02:05PM +0200, Pierre Habouzit
wrote:
> Le mer 2 août 2006 19:51, Iustin Pop a écrit :
> > On Wed, Aug 02, 2006 at 07:42:40PM +0200, Pierre
Habouzit wrote:
> > > and the pyo and pyc files are generated by
your build process. you
> > > have to remove them manually, e.g. using some
find -name '*.pyo'
> > > mantra.
> >
> > The (old) dh_python did remove the .pyc and .pyo
files at package
> > build time, so one did not have to bother with
their removal. Are the
> > new fancy tools not doing this (asks a developer
still not up-to-date
> > with the new python policy)?
> 
> looking at dh_python source, bumping PYCOMPAT to 2 does
not changes that 
> part of its behaviour.
> 
> though, even for the lyx-common in the archive there is
.pyo/.pyc 
> in /usr/share/lyx/lyx2lyx/ (wich in itself is quite
bad).

Ah, then that must be it - it must be invoked as:
  dh_python /usr/share/lyx/lyx2lyx
in order for it to scan other dirs and generate the correct
postinstall/prerm.

Iustin


-- 
To UNSUBSCRIBE, email to debian-python-REQUESTlists.debian.org
with a subject of "unsubscribe". Trouble?
Contact listmasterlists.debian.org

Le mer 2 août 2006 20:09, Iustin Pop a écrit :
> On Wed, Aug 02, 2006 at 08:02:05PM +0200, Pierre
Habouzit wrote:
> > Le mer 2 août 2006 19:51, Iustin Pop a écrit :
> > > On Wed, Aug 02, 2006 at 07:42:40PM +0200,
Pierre Habouzit wrote:
> > > > and the pyo and pyc files are generated
by your build process.
> > > > you have to remove them manually, e.g.
using some find -name
> > > > '*.pyo' mantra.
> > >
> > > The (old) dh_python did remove the .pyc and
.pyo files at package
> > > build time, so one did not have to bother
with their removal. Are
> > > the new fancy tools not doing this (asks a
developer still not
> > > up-to-date with the new python policy)?
> >
> > looking at dh_python source, bumping PYCOMPAT to 2
does not changes
> > that part of its behaviour.
> >
> > though, even for the lyx-common in the archive
there is .pyo/.pyc
> > in /usr/share/lyx/lyx2lyx/ (wich in itself is
quite bad).
>
> Ah, then that must be it - it must be invoked as:
>   dh_python /usr/share/lyx/lyx2lyx
> in order for it to scan other dirs and generate the
correct
> postinstall/prerm.

well actually, with pycompat to 2, it does not generates the
pre/postrm. 
pycentral/support do takes care of that part.
-- 
·O·  Pierre Habouzit
··O                                               
madcoderdebian.org
OOO                                                http://www.madism.org

On Wed, Aug 02, 2006 at 08:14:08PM +0200, Pierre Habouzit
wrote:
> Le mer 2 août 2006 20:09, Iustin Pop a écrit :

Hi guys,

> > Ah, then that must be it - it must be invoked as:
> >   dh_python /usr/share/lyx/lyx2lyx
> > in order for it to scan other dirs and generate
the correct
> > postinstall/prerm.
> 
> well actually, with pycompat to 2, it does not
generates the pre/postrm. 
> pycentral/support do takes care of that part.
It seems that you've to call the dh_py* stuff somewhere
above some other
dh_ commands. I'm not sure which exactly broke it in this
case and I've to
learn for some written tests now so that I can't look
deeper in it.
Maybe you should note that in the wiki page aswell that
it's ok to call it
directly after dh_installman.

Thanks for your support guys!

Sven
-- 
If you won't forgive me the rest of my life
Let me apologize while I'm still alive
I know it's time to face all of my past mistakes
  [Less than Jake - Rest Of My Life]