Rolling Releases for 1.3 (and beyond)

I've just finished testing the new rolling releases system and it finally works 
as i want it:

 - Updates are distributed as sfs files containing deltas and/or new files.
 - The rolling releases script processes incoming new files first, patch the 
   deltas on a temp folder and finally apply the patched files to the system.
 - If the delta patch is for a system-wide lib or application it first declares 
   a temp PATH or LD_LIBRARY_PATH, makes a backup, copies the patched files into 
   the system an then redeclares the original PATH or LD_LIBRARY_PATH, i know 
   this doesn't ensures 100% success and saying "nothing wrong is gonna happen" 
   is stupid but at least it makes it a little safer.

The idea for this system is to avoid uploading isos for minor or patch updates
(following the major.minor.patch versioning).

I've uploaded frankenpup isos since 2009 and tried really hard to make all of 
them worth uploading and with the rolling releases i'll upload isos ONLY for major 
releases or critical minor updates instead of when a base lib is added removed or 
updated or a software is removed or replaced making deployment easier and smoother.

This opens many new challenges for me since i'm no expert programmer but this 
small puplet has been my small plaything for years and i'm willing to take on the 
challenge and give it a try.