[ckan-dev] Source install/deployment docs

[Sean Hammond]

> Hi Sean,
> 
> This sounds like a good compromise to me. I'll defer to David's and Joe's
> judgment on what this does to packaging though.

Just to update the list, we decided to go with this compromise where
both the package and source installs use /usr/lib/ckan/default/ and
/etc/ckan/default/, so that they leave space for multiple CKAN's to be
installed on one server, even if a lot of the time only the default one
actually gets installed.

> I only have one worry with us changing how the package works.  What about
> package upgrades? We should test that people upgrading from 1.8 to 2.0 will
> able to upgrade with the new package and not have problems.

On this, we said that there _will_ be a documented 1.8 -> 2.0 upgrade
process for package installs, but it will be a manual process not
completely automatic.