Comment 36 for bug 1176046

Maybe we are not looking the situation the right way ... What if we look at this the opposite way ?

"isc-dhcp-client" remains the same including the extra random bindings ports.

and we introduce a new package "isc-dhcp-client-noddns" that change the dhclient behavior by overriding dhclient and introduce the disable DDNS feature version of dhclient without the extra random bindings ports.

Assuming that most user will stick with "isc-dhcp-client", then the upgrade will be smooth.

# Use case #1
User that stick with "isc-dhcp-client" that relies on DDNS functionality at release upgrade will have to manually install "isc-dhcp-client-ddns" to have the same functionality as "isc-dhcp-client" in Trusty.

From my understanding, the above is an acceptable behavior ? Please correct me if I'm wrong.

# Use case #2
User that decide to install "isc-dhcp-client-noddns" mean they don't relies on DDNS functionnality, so at next release upgrade, they will get "isc-dhcp-client" and won't notice any change on their side. And if one day they need the DDNS feature, then they will simply have to manually install the "isc-dhcp-client-ddns" package.

Not sure on how feasible it is to introduce a package that will no longer exist in next release upgrade, maybe someone can shed some light on this if it's doable or not.

Does that make sense ?

Eric