On Aug 30, Jean-Christophe Dubacq <[EMAIL PROTECTED]> wrote:
> Instead, all packages should call a common update-inetd minus the last
> line. This common part registers the arguments for the service under a
> common format. Then it calls a inetd-specific script that parses those
We do not have a n
On Mon, Aug 28, 2006 at 12:58:27PM +0200, Marco d'Itri wrote:
> On Aug 28, Roger Leigh <[EMAIL PROTECTED]> wrote:
>
> > 1) Split out update-inetd from netbase into a new "inetd" package.
> No, because e.g. xinetd needs a totally different update-inetd program.
> It's simpler if each inetd package
On Aug 28, Roger Leigh <[EMAIL PROTECTED]> wrote:
> 1) Split out update-inetd from netbase into a new "inetd" package.
No, because e.g. xinetd needs a totally different update-inetd program.
It's simpler if each inetd package will ship its own update-inetd.
> 3) All update-inetd users need to dep
Hi folks,
Following the last thread on the subject, several things have
happened:
1) All packages depending on netkit-inetd have had their dependencies
replaced with a netkit dependency.
2) netkit now only depends upon openbsd-inetd, so netkit-inetd is now
no longer used by either new insta
4 matches
Mail list logo
