Bug#82609: Abuse of debconf
On Wed, Jan 17, 2001 at 09:21:22AM +0000, Paul Hedderly wrote:
> The package has now scrapped the propper text based config
> file and stores it's configs in debconf. Debconf is not meant to be
> a central hidden binary configuration pool, or "registry", it is only
> there to prompt the user in a convenient and consistent manner!
I created lsdoom.conf originally to track whether the executable was made
suid by the user or not. It was used only by package installation, and
never by the package. Is it, therefore, wrong for me to query debconf
for the state the user has chosen? Or should I re-instate lsdoom.conf (which
consisted of one line: is_suid=y/n), which duplicates the information
in debconf, and query that instead?