On Fri, 2007-05-11 at 10:32 +0200, Michael Holzt wrote: > > That _is_ the question. However, I looked at qmail (debian src package) > > and it also depends on adduser. I looked briefly at the policy manual > > but didn't find anything there. I thought that the Debian maintainer > > might know the answer. I need to look at the package anyway. > > Now i think there is no policy here. A debian package must depend on all
Thanks. > the tools needed and if the package maintainer decided to use adduse in > the (pre/post-)installation scripts, the package must depend on it. I'm Ah ... you are right. The call to adduser is in qpsmtpd.postinst. In that context, it is simpler to use adduser ... i wonder if I'll be able to change that. > a debian maintainer as well and i have a package which must depend on > update-inetd because it _can_ be used with inetd and uses update-inetd > to update the config in this case. Had to read that carefully but it seems reasonable. > > This is the downside of having packages which are universal enough to > be usable by lots of users with different requirements and have therefore But the upside is having "lots of users" ;-) > lots of dependencies on libraries, tools, etc. I have recently tried to > build a "minimal" chroot jail to run e.g. php-cgi. Just for this you have > to install about 60 (!) other packages. I really dislike this because i'm > quite a purist but i guess this is the price of a universal operating > system. But one dependency more or less doesn't change anything at all > regarding the general problem so i believe that discussing if qpsmtpd > should depend on adduser or shouldn't won't help much for the overall > result. I might build a debian package for trunk if I get time ... but I can see clearly where the dependency is now. > > > Regards > Michael -- --gh
