Making opkg non-interactive (removing config file conflict resolution question)

[Alexandros Kostopoulos]

Hi all,
being non-interactive, as Thomas proposes, seems the right thing to do for  
embedded systems. However, a config file option (or even a
compile-time option) would be nice, in case someone wants to use  
interactive mode. Or perhaps, there could be an command line option (e.g.  
-y - answer yes to all questions) in order to select non-interactive mode.

However, in any case, I think that the right think to do, in  
non-interactive mode, is to preserve the OLD config file, and maybe backup  
the new one.

Alex

On Mon, 14 Apr 2008 17:04:02 +0300, Thomas Wood <thomas at openedhand.com>  
wrote:

>
> Currently, the only place where opkg asks for user interaction during a
> transaction is when a package is upgraded and the existing configuration
> file has been modified.
>
> PackageKit requires that the package system is as non-interactive as
> possible and cannot handle questions during transactions.
>
> Therefore, I would like to propose removing the configuration file
> upgrade question and instead simply backing up the existing file and
> installing the new one, or installing the new one straight into an
> alternative location. The user can then be notified of the change and
> can take action appropriately.
>
> As I see it, it makes much more sense for an embedded package manager to
> be completely non-interactive. The question is, which of the two
> possible conflict resolution options is most ideal.
>
> Does anyone have any particular views on this?
>
> Regards,
>
> Thomas
>