Re: design issues in debian packages

[Brian May <bam@debian.org>]

>>>>> "Adam" == Adam Heath <doogie@debian.org> writes:

    Adam> The way I am solving this for jboss, is to have a .foo to
    Adam> match each foo in a .d, where .foo is executable, and this
    Adam> .foo is what checks to see if the configuration fragment(as
    Adam> I call them) should be used.  My goal is to make this script
    Adam> generic(so far, it is), and have it be included into
    Adam> debianutils.  This script also handles the case of .rpm-save
    Adam> and .dpkg-new type files, and skips over them.

I was thinking of the ideal long term solution:

For each file in *.d/$file, package $file must be installed, otherwise
it will get ignored.

For shell scripts it is easy enough to put a test in at the top (like
for init.d files), similar things can and are done for cron jobs, but
this can't be applied for /etc/logrotate.d or /etc/devfs/*.d.

Yuck!
-- 
Brian May <bam@debian.org>