start-aliendalvik-preinit.sh

Thank you very much for your explanation. It seems I have overlooked that little dash. So I could delete that line. But the questions arises if the developers might had the intention to change this line to something else and have forgotten to do that... Best regards, Uwe.

I think the answer above is plausible. Based on that, it makes sense that they would want to execute it if it exists, and not fail if it doesn't. The only consequence being that if the script legitimately fails, it wouldn't be noticed. So a wrapper may have technically been a better option. Another way would be to detect whether it's needed at build time. But then that would likely require separate packages for different situations, which would complicate things a lot when defining how dependencies work.

On the flip side, if it's something like indexing, or cleanup, maybe it's not considered important as to whether it succeeds or fails.

But more likely, it's intended to run-once (Eg to make sure directories are created) and delete itself on success. And this was simply a convenient way of achieving that without over-complicating things.

Another possibility is that it's future proofing for something in an up-coming version.

In any case, I'd leave it alone, unless there's a reason you want to mess with it?

This sounds very plausible. So I'll leave my hands off... Best regards, Uwe.

Whoops, I hope I didn't put you off. I could have worded that last sentence better. I definitely encourage tinkering. :)