The following guidelines should be followed when uploading Clients

1)  The client binary should be named as "dnetc" do not include 
    os-platform in the name of the binary file.  You may add an 
    extension such as .exe to the end of the file name where the 
    extension is normal for the os/platform

2)  All client packages should include the following files
      dnetc
      DOCS/dnetc.txt   
      DOCS/CHANGES.txt
      DOCS/readme.os  (include the readme for the proper os)

3)  All clients packages (tar.gz, zip, bin, etc...) must be PGP signed 
    for release.  If you do not have access to PGP, get it.  All 
    un-signed clients will be discarded and you will be asked to 
    resubmit a client.  All client packages must unarchive/untar to 
    the base directory the user is unarchiveing/untaring the archived 
    file to.  In other words dnetc440-linux-x86.tar.gz should not 
    untar to "./dnetc440-linux-x86/"  it should untar to "./"

4)  All clients packages and their sig file must be uploaded to 
    upload.distributed.net in the incoming directory

5)  Client Package names should follow this basic name outline.  You 
    may discard options that are not relevant. Such as win32 would not 
    have a binary format or library.
      
      dnetc###-osandver-arch-binaryformat-limitations.archiveextension
      
6)  Mail must be sent to coders@lists.distributed.net and include the 
    following information:
      - Porter's Full name
      - e-mail address you can be contacted at
      - specific platform client was built for cpu range os range
      - special instructions about the binary

7)  Update builder.txt
