Re: Bug#12869: debmake still uses #!/bin/bash for very simple scripts.
On Thu, 18 Sep 1997, Christian Schwarz wrote:
>As it was not really a bug, I didn't report a bug report--but you're
>right, I probably should have done this either way.
>
>If I recall right, the problem was that debstd inserted calls to
>"update-rc.d" and "/etc/init.d/foo start" to the postinst script
>automatically, which I wasn't aware of in the first place and couldn't
>turn it off after I realized this. (So it would be nice if there was an
>option to debstd to tell it not to touch the maintainer scripts--just
>install them, chmod them, etc.)
Removing debian/init.d would have removed these calls from the script.
>But please don't get me wrong; as I said debmake is really a great tool
>for easy packages. However, I spent much time with the mysql package to
>get it compile and have everything working to get the packages right.
>Since I really set up the debian/* files with care I can't afford using
>debstd since I don't know what it's doing _exactly_. And since it's not
>actually doing too much (debstd was replaced with a few additional lines
>to debian/rules without much troubles) I think it's better to do these
>things "by hand" in larger and more complicated packages.
That might be true. Debmake tries to make general things easier. It tries
to stay out of the maintainers hairs if he does not wish it to do
anything. I have repeatedly switched off certain functionality for certain
packages that just needed to have things done a different way.
You can simply know what its doing by looking at the output or the script.
>Do you see an easy way to write such a debstd replacement which just
>prints the commands to stdout? I had a short look at debstd but I don't
>see an easy solution right now.
Debstd is interactive in many ways depending on its own output from prior
stages. This is not the way debstd was designed.
--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
Reply to: