On Jul 24, Magnus Holmgren <[EMAIL PROTECTED]> wrote: > Anyway, you have proposed that all superserver packages provide their own > update-inetd implementation, which is fine and simple enough, except that > it's not clear how the configuration would be transferred when one > superserver is replaced by another. There needs to be some common data update-inetd would update its own little database when called by postinst. It's not a beautiful design, but it allows users to modify /etc/inetd.conf and maintainers to not modify their own packages.
On Jul 23, Pierre Habouzit <[EMAIL PROTECTED]> wrote: > IMHO the problem is easy to solve, I'd go this way: Have a registry in > /etc/ with a simple syntax (like ini-style), that would be a superset of > all the features in all supported superservers. Local administrators > would have to edit those files to make their local changes. This is what makes it unacceptable. > The downside of this proposal is that every package using a super > server would have to be updated, but OTOH that is not a big number of > packages: > > $ grep-dctrl -s Package -FDepends netkit-inetd -o -FDepends > inet-superserver -o -FDepends update-inetd \ > /var/lib/apt/lists/mad_debian_dists_sid_main_binary-amd64_Packages | wc > -l > 51 This lists only a small part of them, most ones still depend only on netbase. -- ciao, Marco
signature.asc
Description: Digital signature
