> Although it still is a possibility to use an external dhcp client, my > preference still goes to a small, internally coded dhcp client since you > won't add any dependencies. The reason I think it is quite easy is that I > don't want to implement it with a large feature set, we only have to send > two packets and receive two packets.
I'm still hesitant - i mean, dhclient is so core to any modern distro that it is even installed in an etch debrootstrap, and that is a pretty minimal environment... And its trivial for the packagers to add a dep on it... I'm taking this stance mainly because I hate the very notion of having multiple versions of the same thing, even though in this case thats not exactly what would be happening... its still reimplementing a subset of dhclient.. I mean, if you took the no dependencies thing far enough, there would be no python and we'd use an internally coded WBXML and XML library that only implemented the subset of XML and WBXML we need... Just playing devils advocate... John ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
