This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
pld-gitolite [2012-04-03 11:00] draenog [Restrictions on committed files] |
pld-gitolite [2012-04-05 17:35] draenog [New package creation] |
||
---|---|---|---|
Line 52: | Line 52: | ||
===== New package creation ===== | ===== New package creation ===== | ||
- | In upstream version of gitolite, new package is created by cloning of no existing repo (if the access rules allow for it). However I think that it is too error prone. So [[https://github.com/draenog/gitolite|gitolite was forked]] and an option to disable creation of wildcard repositories was added. Instead an [[http://sitaramc.github.com/gitolite/doc/admin-defined-commands.html|admin defined command]] was created for this task: | + | In upstream version of gitolite, new package is created by cloning of no existing repo (if the access rules allow for it). However I think that it is too error prone. So [[https://github.com/draenog/gitolite|gitolite was forked]] and an option to disable creation of wildcard repositories was added. Instead an [[http://sitaramc.github.com/gitolite/ADCs.html|admin defined command]] was created for this task: |
ssh draenog@carme.pld-linux.org create <new_repo> | ssh draenog@carme.pld-linux.org create <new_repo> | ||
=====Package deletion===== | =====Package deletion===== | ||
- | People with write access to gitolite-admin repository can use [[http://sitaramc.github.com/gitolite/doc/admin-defined-commands.html|admin defined command]] to move obsoleted packages to attic space: | + | People with write access to gitolite-admin repository can use [[http://sitaramc.github.com/gitolite/ADCs.html|admin defined command]] to move obsoleted packages to attic space: |
ssh draenog@carme.pld-linux.org trash <repo> | ssh draenog@carme.pld-linux.org trash <repo> | ||
| |