LinuxMusicians

Here's how we handle updates to NBO. It's going to be a "rolling release" model.

You've already downloaded and "installed" the full NBO package named "nbo.zip". We'll call that a "master package". Everything is organized into one master "NoBudgetOrch" folder.

Now when an update happens, the update zip file contains only those files that have actually changed. And they too are organized into one master "NoBudgetOrch" folder. So if you unzip the update into your existing NoBudgetOrch folder, it will automatically update your full NBO installation. This first update file is named nbo_update_0_1.zip. The 0 indicates it is for version 0 of the master package. The 1 indicates it is the first update. If there is another update zip released, it will be named nbo_update_0_2.zip. A third update package would be named nbo_update_0_3.zip. You apply them in the order that they're released. Since update zips contain only files that are changed, they will typically be very small. (This first update I'm releasing alters four instruments, and is only 13.7 meg).

After about 10 update zips, then a new master zip package will be released. It will be named nbo_1.zip. This is now version 1 of the master package. And it will have all the previous updates applied to it. If you've applied all the update zips, you won't need to download the master package again. Your current installation will effectively be the same thing. And then any subsequent update zips will be applied to this master package. The first update zip will be named nbo_update_1_1.zip.

If you ever get out of sync, you can download the latest master zip, and all the update zips for it. That brings you uptodate.

Note to FaTony: The web site will not need to store older master/update zips. Only the latest master zip, and any update zips specifically for it.

Attached is a torrent for the update zip.

Just an idea:

Can you perhaps put version.txt file in the root directory that gets updated whenever you apply an update so it's easy to see which version you have?

Or, alternatively, a text file for each zip, so you can easily see which updates you have applied? E.g. if your root directory contains the files nbo_1.txt, nbo_update_1_1.txt and nbo_update_1_2.txt, you know which version you have and which updates you have applied.

Maybe just make a torrent where everything is unzipped so ppl can just point their torrent client to the directory and have it updated?

Also, maybe call updates nbo_X_update_Y.zip? Like nbo_0_update_1.zip.