Please sign in to comment.
(please read full commit message) upgrade behaviour changed
**upgrades no longer touch the config or the keydir** When you first install gitolite, the easy install script has to do two *distinct* things: * install the software * create and seed the gitolite-admin repo with a minimum config file and the newly created pubkey That's fine for an install, because nothing exists yet anyway. Subsequent invocations of the script should only do the first task (so that gitolite itself can be upgraded), and not attempt to fiddle with the config file and pubkeys. Unfortunately, until now I had not been separating these two activities cleanly enough. For instance, the commit message for 8e47e01 said: IMPORTANT: we assume that $admin_name remains the same in an upgrade -- that's how we detect it is an upgrade! Change that name or his pubkey, and you're toast! Ouch! So now I decided to clean things up. The "Usage" message tells you clearly what to do for an upgrade. Should have been like this from the beginning, but hey we got there eventually :) ---- Code-wise, this is a major refactor of the easy install script. It uses an old forgotten trick to get forward refs for bash functions ;-) and in the process cleans up the flow quite a bit.
- Loading branch information...
Showing with 358 additions and 242 deletions.
Oops, something went wrong.