[Freedombox-discuss] How do we handle package upgrades on the Freedombox?
- Subject: [Freedombox-discuss] How do we handle package upgrades on the Freedombox?
- From: james.valleroy@gmail.com (James Valleroy)
- Date: Thu, 26 May 2016 07:47:38 -0400
- Message-id: <[🔎] CAG3_j1TagnDS=Ty2J8UgT22ARQYiqP_XsTHK0kDX5+iTLjKzpQ@mail.gmail.com>
- In-reply-to: <20140417085712.GC28492@ulrik.uio.no>
- References: <20140414204130.GH28492@ulrik.uio.no> <20140414220543.4364.76936@bastian.jones.dk> <87ppkigpi3.fsf@gmail.com> <20140416083736.4364.35047@bastian.jones.dk> <20140416085456.GQ28492@ulrik.uio.no> <20140416120425.4364.42243@bastian.jones.dk> <CAG3_j1RxAZre1ZrVCeoqvuZjw5iQKY-_J0Pnhqf=i7Q0QnjOVw@mail.gmail.com> <20140417011635.4364.80942@bastian.jones.dk> <20140417062022.GA28492@ulrik.uio.no> <20140417082920.4364.31075@bastian.jones.dk> <20140417085712.GC28492@ulrik.uio.no>
On Thu, Apr 17, 2014 at 4:57 AM, Petter Reinholdtsen <pere at hungry.com> wrote:
> [Jonas Smedegaard]
>> Seems to me that you are basically arguing that debconf in its
>> current form only legally works on initial install and interactively
>> by admins - not as automated reconfiguration by other packages.
>>
>> Is that correctly understood?
>
> Almost. The current tool set have those features. I suspect debconf
> with appropriately implemented packages can be used (ie using yet to
> be written tools to "fake" the interactively by admins part) to do
> this.
>
> Debconf have support for replacing both the frontend/gui and
> backend/database, and I suspect this might be used for automated
> reconfiguration of packages. But I am not sure, and have never seen
> this done.
>
> This is the background for my suggestion to prefer .d setup or
> multilevel setup, which I know work. :)
First, sorry for reviving a 2-year old thread. But I finally came
across an answer to the question of using debconf for non-interactive
re-configuration. :)
The approach described here uses DEBCONF_DB_OVERRIDE:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825107#15
It looks a bit clunky, but it works, and allows the package to remain
policy-compliant by reading configuration values from disk in the
normal case.
Reply to: