Thread: [Announce] busybox-power for Harmattan
View Single Post
iDont is offline iDont
2012-11-23 , 19:47
Posts: 268 | Thanked: 1,053 times | Joined on May 2010 @ The Netherlands
#19
Originally Posted by wolke View Post
i understand the desire to caution users away from installing packages that could very easily brick their phone if something unforeseen goes wrong. thats what warnings are for.

that doesnt mean its ok to forcibly require user intervention during a deb install, ever. ESPECIALLY when you require an x server and dbus session...

it makes it impossible to install as part of an automated restore script, without seriously going out of your way {e.g.: temporarily replacing the callable binary with a script that just cats the file passed in and exits with 0}.

i personally just remove the preinst because i know im on an n9 and i know i want to install the package, but it would be nice if you wouldnt put installation guis in deb files in the first place.
Thank you for your feedback, appreciated. However, I'm not in favor of removing the warning, because:
  • It's only shown during first time installation (upgrades or re-installations won't trigger it).
  • More importantly: I think it is a very sane warning. Take kernel-power for Maemo for instance: most users will not doubt that it is rock solid. However, kernel-power can't guarantee 100% compatibility with the stock installation, just like I can't with busybox-power. I have all faith in busybox-power for Harmattan -the download statistics for its older brother are very reassuring as well-, but I think it's only fair to warn users the way it's currently done (disregarding the fact that there isn't really an alternative way to do it, unfortunately)

Nonetheless, you're making a very valid point: the current implementation does not allow unattended installations of busybox-power.
Therefore I would like to suggest a compromise: what if I would let the preinst script check for the existence of a file (e.g. /tmp/.bbp-unattended), and if found, it'll exit 0 straight away. Since you're already automating installation, you would only need to put an extra "touch $file" in your script prior to installing the deb. Let me know if this works for you and I'll implement it and document it in the OP .
 

The Following 2 Users Say Thank You to iDont For This Useful Post: