arch patch queue manager
Georg Seidel <[email protected]>
| Newsgroups | gmane.comp.video.gephex.devel |
|---|---|
| Message-ID | <[email protected]> |
Just installed the arch-pqm-0.4 on gephex.org.
The setup is almost complete:
- created user gephex
- added ~/.procmailrc to user gephex which lets arch-pqm read
the incoming email
- creates ~/.arch-pqm.conf for user gephex
(changed some default settings s.t. all stuff happens inside
/home/gephex)
- configured arch-pqm to verify signed emails with gpg
(so far, I only added my public key to the keyring)
- added [email protected] to /etc/postfix/virtual
- installed python 2.3.3 to /usr/local
What still needs to be done:
- cron job that calls arch-pqm --run
- add hook script that sends commit emails
- create one branch of gephex--main--0.4 and gephex--main--0.5 for
every developer and tell arch-pqm where it is
(those branches can be on different archives, so for example martin
could have his archive on tyr, I could mirror my offline archive
to gephex.org, ...)
- add other public keys to gephex keyring
- change permissions on /var/arch/gephex s.t. only user gephex has
write access
When setup is complete, it could work roughly like that:
Let's assume coma did some changes on his branch (for example he
finnished the gui).
So he commits everything into his branch and sends an gpg signed email
with some fancy content to [email protected]
(http://web.verbum.org/arch-pqm/#id2799119).
His merge request is stored in the queue and the merge is performed
the next time "arch-pqm --run" is executed.
If there are no conflicts, we will get a nice commit message via
email.
Regards,
Georg