To: CISC220-010-04S@UDel.Edu, paddock@mail.eecis.udel.edu
Subject: Project submission
Date: Fri, 20 Feb 2004 10:03:45 -0500
From: "Dave Saunders" <saunders@mail.eecis.udel.edu>

The due date for phase 1 of project 1 is moved to next Thursday,
February 26.  This will allow time for us to review the 
submission protocol in class Tuesday, and it will also give you
a chance to consult your TA, Todd Paddock, in his office hours
Tuesday and Wednesday with any last minute questions.

Best, -bds

-------------------------------------------------------
The submission protocol is this:

The submission form for projects will be by email of a "tarball"
to the TA, Todd Paddock, paddock@cis.udel.edu.

The tarball may be the body of the message or the single attachment.
It is a tarball, since our projects involve multiple files and "tar"
is a good tool to bring everthing together in one object.  The "tar"
command has a long history.  It's name stands for "tape archive", but
it has evolved from that to be a general tool for packaging up large
projects.

Do this:
1.  Create a subdirectory labeled with your name and the project id.  
Thus if your name is Smith and the project is phase 1 of hw 1:

> mkdir smith-hw1a
> cd smith-hw1a

2.  Develop and test your solution in this directory, including all 
necessary files.  Have a Makefile such that if a person enters just
"make" in this directory, the executable is created.  Thus the 
final target should be the first target listed in the Makefile.

3.  Prior to submission, clean up this directory.  This means
no a.out, no executable, no .o, no core, no random fragments of code
not actually part of the submission.  In other words, back things up
to pure source, source from which the executable (and perhaps some .o's) 
can be made with a call to "make".  For this purpose, it is convenient to 
have a "clean" target in your Makefile that removes all files resulting 
from compilations.

4.  Build the tarball: go to the parent directory, create and submit
smith-hw1a.tar.

> cd .. 
> tar cvf smith-hw1a.tar smith-hw1a
> ...email smith-hw1a.tar to paddock@cis.udel.edu 

On the tar command, the "cvf" is options meaning: c - create an archive,
v - be verbose about it (the tar command will display the names of the 
files being included in the archive), f - put the archive in a file
named next (i.e smith-hw-1a.tar).  The file suffix should always be .tar. 
The final argument on the tar command line is the directory which is
to be tarred up.  

Let there be no confusion: replace the "smith" of this example by your 
own last name!  The name is important so that your submission does not
get mixed up with others.  If you develop in a directory of another name,
say frobdir, rename the directory with the mv command before tarring:  
> mv frobdir smith-hw1