On Wed, Apr 16, 2014 at 8:04 AM, Jonas Smedegaard <[email protected]> wrote: > Quoting Petter Reinholdtsen (2014-04-16 10:54:56) >> can you add some details to the page on how the freedombox project can >> use debconf to change the setup we apply to packages after >> installation? For example, if the tor package started using debconf >> and we used debconf to configure tor during installation, and after >> installation wanted to change the freedombox setup for tor, how would >> that be done using debconf? We already had that need when we enabled >> SOCKS in tor a few weeks ago. > > There's two parts to debconf: > > 1) Implement debconf question(s) about SOCKS in tor package. > 2) Preseed all non-default answers, and seed them to tor package. > > First is the hard one, but also the one most likely that we can all > help out with by identifying needed tweaks and having a dialogue with > package maintainers on how they might be persuaded to adopt debconf. > > Second is specific to Plinth, and should be documented in manpages of > debconf. For an equivalent implemented in shell it would involve > "debconf-set-selections" and "debconf" commands (not the common wrapper, > "dpkg-reconfigure", as it forces use of an interactive frontend).
I think we can use dpkg-reconfigure without the interactive frontend: echo "jwchat jwchat/ApacheServerName string $hostname" | debconf-set-selections DEBIAN_FRONTEND=noninteractive dpkg-reconfigure jwchat Do you see any issues with this approach? _______________________________________________ Freedombox-discuss mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
