Joey Hess writes:
> Steven Hamilton wrote:
>> dh_installinit incorrectly detects a shell script, intended for /usr/games
>> (detailed in <package>.install), as an init script and builds it in
>> /etc/init.d
>> This only appears to occur when the script is named the same as the package.
>
> I don't think that dh_installinit ever "detects" anything. It only
> installs the init scripts listed in debian/package.init or debian/init.
>
> If you think otherwise, you need to provide a test case showing the
> problem.
No probs. To recreate;
1) Create package with <packagename>
2) Create a bash script to launch your binary with the name <packagename>
#!/bin/bash
love /usr/share/games/mrrescue/mrrescue.love
3) Create <packagename>.install file to copy your script into /usr/games;
debian/<scriptname> usr/games
4) Create rules file;
%:
dh $@ -Pdebian/<packagename>_build
(-P is used to remove conflict of tmpdir with <packagename>)
Result;
The debian/<packagename>_build dir will have your script placed in
/etc/init.d/<packagename>
Putting override_dh_installinit: in rules works around this and places
the script in /usr/games as requested by the .install file.
I have a guilty package exhibiting this behaviour currently on mentors;
https://mentors.debian.net/package/mrrescue
--
Steven Hamilton
I don't look like two zombies
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
