On Tue, Apr 20, 2010 at 06:22:40PM +0200, Julian Andres Klode wrote:
> > The package should run update-command-not-found on installation,
> > possibly asking a debconf question first. It should also do this on a
> > regular basis via a cron job. (This could be enabled/disabled via an
> > entry in /etc/default/command-not-found.)
>
> Ask-and-do-once debconf questions are not the nicest thing
> to do. The cron job also seems interesting.
Fair enough. Although then my personal preference would be to run
update-command-not-found on upgrade (or at least on install); I, for
example, missed the message during the installation.
Here is my trivial cron.weekly job:
#! /bin/sh -e
test -x /usr/sbin/update-command-not-found \
&& update-command-not-found &>/dev/null
exit 0
> But in my opinion, command-not-found should ship a pre-built
> database and offer update-command-not-found as an optional
> tool, mostly for users of unstable. That's also stated in
> the TODO section in README.Debian.
Hmm, you could do that, but then you run into questions of: where do
you store this database? How do you not overwrite a user-updated
database when upgrading the package but update an out-of-date
database? Surely generating it at install-time is the way to go?
Julian
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
