From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: GSoC: Rohan to work on DHCP client Date: Thu, 30 Apr 2015 10:23:17 +0200 Message-ID: <87k2wu58ju.fsf@gnu.org> References: <87vbgeiwvz.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: (Rohan Prinja's message of "Thu, 30 Apr 2015 01:12:56 +0530") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org To: Rohan Prinja Cc: guix-devel , guile-user@gnu.org List-Id: guix-devel.gnu.org Hi Rohan, Rohan Prinja skribis: > Also, how do you suggest I get started with the pre-coding period? I > was thinking of rereading the ISC dhclient code, this time more > carefully, Sounds good. > and in parallel, adding some packages to the Guix to get a feel for > how porting packages to the archive works. This is a nice thing to do ;-), but it=E2=80=99s obviously not really neede= d for the DHCP work itself. > Once I'm done reading dhclient, I could start on designing the CLI. Is > this fine or do you think an alternate plan of action would be better? I guess the CLI will be very similar to =E2=80=98dhclient=E2=80=99, so I wo= uld recommend not spending too much time on it at the beginning. I think the crux will instead be API design, basically refining what you describe in the proposal under the =E2=80=9CMay 25 - May 31=E2=80=9D headin= g. A good idea would be to write a hypothetical =E2=80=98main=E2=80=99 procedure of a= DHCP client program that would use the DHCP module. HTH, Ludo=E2=80=99.