c4069dd85f
**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
|
||
---|---|---|
.. | ||
0-INSTALL.mkd | ||
1-migrate.mkd | ||
2-admin.mkd | ||
3-faq-tips-etc.mkd | ||
5-delegation.mkd | ||
6-ssh-troubleshooting.mkd | ||
COPYING | ||
TODO |