Re: Creating /usr/bin/ entries to scripts the right way
On Mon, Jul 30, 2007 at 11:27:35AM +0530, Kumar Appaiah <akumar@ee.iitm.ac.in> wrote:
> On Mon, Jul 30, 2007 at 07:39:59AM +0200, Mike Hommey wrote:
> > This is just the fine way. Or, for 2 lines, you can directly write them
> > in debian/rules. BTW, I would recommend you to, and to hard code the
> > python version in the script provided by the package instead of using
> > pyversions at runtime : if your package is built for python 2.4 and 2.5,
> > and is installed when python 2.6 becomes default, it will stop working.
>
> That's a good point. But I would like you to elaborate on this.
>
> 1. How do I put this in rules? Will this be OK:
>
> echo -e "#!/bin/sh\nexec /usr/bin/python2.4 \
> /usr/lib/python2.4/site-packages/HarvestMan/harvestman.py \"$@\"" > harvestman
>
> (It seems to dump the required thing!).
>
> 2. As you see, in the above string, I have hard coded python2.4. I
> guess, when Python 2.5 becomes "current", I just make another
> upload with Python 2.5 as current. Is that correct?
Well, you can use pyversions -d in debian/rules. You'll only have to ask
for a binNMU when python 2.5 becomes current.
Mike
Reply to: