TODO
====
o MySQL usage
	* Header to be stored in MySQL as tables.
	* Provision for "only size" option so as to gauge the size of the patch 'to be downloaded'.

o User-Interface
DONE:	* Enable viewing of the kernel directory structure using KConfig.
	* Enable updation feature from within Kconfig.
	* Displaying the versions of each sub-system while browsing this directory structure in Kconfig, 
	  or have a separate option to browse the kernel directories to view the version structure. 
	* The version browsing UI should query the server for the the size of patch that selected,
	  to give an estimate of how big the patch would be.

o Enable calling server with specific directories with the from-to version numbers. 
  (Currently, we only have a from-to version support for a complete kernel download).

o While creating the source .sc files, include name of all source directories and append a zero 
  if no updates are being sent to client. This would allow all those directories with no updates 
  in the required versions, to be marked as 'updated'. (Although this is not required in most cases, 
  but there could be times when a required directory although has no update, would be displayed 
  as 'not updated').

o Download size required

o Download filename required

o During updation, ALL directories should have a small file depicting their current version
  (for e.g. ".dir-version"). This would help in knowing about the version of the directory in
  question on subsequent queries.
	* Or, we could rather have a default status of 'version file not required' policy, wherein,
	  we would need to have a specific file for a directory only when the directory has 
	  a different version number with respect to the kernel root.
  	  	* One thing in this is that we would still need to have a '.dir-version' file created 
  	  	  in the patch assuming nothing about the method of the update. i.e., if the update 
  	  	  was done by hand, the .dir-version would atleast maintain the version integrity of 
  	  	  the directory.

o All scripts to use PHP functions rather than OS specific commands (like bzip, gz, etc...)
	* That is 'exactly' why we have the hash / compression alternatives provided in the 
	  compression format !!!
	* This would ensure that the scripts would work across operating systems, especially when 
	  using it in windows / unix based environments.

o Documentation required
	* Patching issues
DONE:	* Brief working documentation (5th May, 2005)
	  
DONE: o All the scripts to be changed to work on PHP. (1st May, 2005)

v0.1: (released on 12th September, 2003)
========================================
DONE: o Rectify the stupid error around "\n" and make that format common to all scripts.
DONE: o Remove offset for custom patches. offset only required for server patches.
DONE: o Brief documentation, architecture introduction.