[avahi] autotooling python scripts

[Lennart Poettering]

On Tue, 02.08.05 23:19, Sebastien Estienne (sebastien.estienne at gmail.com) wrote:

> 
> 2005/8/2, Joe Shaw <joeshaw at novell.com>:
> > Hi,
> > 
> > On Tue, 2005-08-02 at 21:34 +0200, Sebastien Estienne wrote:
> > > > Ah, ok, in that case you could just make sure that it is a+x, put
> > > > "#!/usr/bin/python" at the top, and stick it in /usr/bin sans .py
> > > i also saw #!/usr/bin/env python
> > > what is it about?
> > 
> > It just sets up the environment and then executes python.  The right
> > thing to do that will work for all distributions is to have a .in file
> > which actually has "#!/usr/bin/env @PYTHON@", put AM_PATH_PYTHON in
> > configure.in, and have it generate the actual script.
> > 
> i wanted to do it like this, the only drawbacks is for developpers, we
> can't really test in the working dir we need to ./configure 
> script.py.in -> script.py.in, add features in scrupt.py, and backports
> them in script.py.in
> Maybe i'm missing something

mhhm? autoconf does this for you. Just edit *.in and type "make",
avahi will run "config.state" for you on the file you changed.

Lennart

-- 
Lennart Poettering; lennart [at] poettering [dot] de
ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.de/lennart/