I intend to orphan the ifenslave package.

I no longer have any time to work on it. The package has an important
bug that should be fixed. Linux bonding interfaces use a controversial
naming scheme (master/slave, and the package name itself reflects this).
If you adopt this, I suggest changing the package name to "bonding", and
replace the master/slave terminology with parent/child.

ifenslave used to be a standalone binary that sent ioctls to the kernel,
but nowadays bonding can be configured via the "ip" command from the
iproute2 package, and by writing to the /sys/ tree. The package no
longer contains the standalone binary, but just provides hooks scripts
for ifupdown.


The package description is:
 This is a tool to attach and detach slave network interfaces to a bonding
 device. A bonding device will act like a normal Ethernet network device to
 the kernel, but will send out the packets via the slave devices using a simple
 round-robin scheduler. This allows for simple load-balancing, identical to
 "channel bonding" or "trunking" techniques used in switches.
 .
 The kernel must have support for bonding devices for ifenslave to be useful.
 This package supports 2.6.x kernels and the recent 3.x.x kernels.
 This is a tool to attach and detach slave network interfaces to a bonding
 device. A bonding device will act like a normal Ethernet network device to
 the kernel, but will send out the packets via the slave devices using a simple
 round-robin scheduler. This allows for simple load-balancing, identical to
 "channel bonding" or "trunking" techniques used in switches.
 .
 The kernel must have support for bonding devices for ifenslave to be useful.
 This package supports 2.6.x kernels and the recent 3.x.x kernels.

I suggest that whoever adopts ifupdown will also take ifenslave and just
fold it in ifupdown, because since it only contains scripts then it does
not make any sense to keep it around as a standalone package anymore.
Hence also brilliantly solving the issue with the s-word.

Also, modern systems are supposed to migrate to the "new" teaming
driver, but AFAIK it is well integrated only in NetworkManager.