For the benefit of anyone reading this who doesn't want to spend hours digging through the archives to figure out exactly what's going on:
Marco's original plan from 2002: http://lists.debian.org/debian-devel/2002/09/msg01532.html Marco's recent revised plan: http://lists.debian.org/debian-devel/2006/09/msg00208.html AJ's description from 2002 of what needed to be done to update-inetd: http://lists.debian.org/debian-devel/2002/09/msg01582.html AJ's most recent attempt to finish rewriting update-inetd: http://lists.debian.org/debian-devel/2006/08/msg00533.html List of packages depending on netbase: http://lists.debian.org/debian-devel/2006/08/msg00561.html A description of available inetd packages: http://lists.debian.org/debian-devel/2006/08/msg00483.html And a basic summary: +all packages depending on netkit-inetd have been updated to depend on other packages instead +openbsd-inetd has been updated to provide inet-superserver and replace netkit-inetd +netbase has been updated to depend on openbsd-inetd|inet-superserver instead of netkit-inetd -other inetd packages now need to be updated to provide inet-superserver -other packages which require an inetd now need to be updated to depend on inet-superserver -post-etch, netbase will be updated to remove the openbsd-inetd|inet-superserver dependency -netkit-inetd can now be removed from debian as it is severely obsolete +openbsd-inetd has been updated to depend on tcpd +netbase has been updated to remove the dependency on tcpd -other inetd packages now need to be updated to depend on tcpd if necessary +the update-inetd script has been removed from netbase and put in it's own update-inetd package +openbsd-inetd has been updated to depend on update-inetd -other inetd packages now need to be updated to either depend on the update-inetd package or provide their own update-inetd script does a new common interface for the update-inetd script need to be defined? or has it already been defined by one of the partial re-writes of the script? or is the old update-inetd interface going to live on in whatever new scripts are written? +/etc/init.d/networking has been pretty much stripped down to 'ifup -a' and 'ifdown -a' -/etc/init.d/networking should probably now be moved to the ifupdown package Once all this is straightened out, what remains of netbase will be very minimal - (protocols, rpc, and services files in /etc/, and a dependency on ifupdown and ping). Since ifupdown and iputils-ping are both priority important, the dependency can probably be safely removed, although any package that actually depends on ifup/ifdown/ping should be updated to depend on those just incase a user decides to try to remove those packages. The 3 remaining files could probably be moved to another package (base-files is the most likely candidate), and netbase could probably be gone completely. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
