Sisyphus repository
Last update: 2018-07-16 08:07:11 +0400 | SRPMs: 18595 | Sign in or Sign up
en ru uk br
ALT Linux repositories
hide window
Sisyphus: 0.5-alt1.1.1.1
p8: 0.5-alt1.1.1.1
p7: 0.5-alt1.1.1.1
t7: 0.5-alt1.1.1.1
Platform6: 0.5-alt1.1.1
t6: 0.5-alt1.1.1
Platform5: 0.5-alt1.1
5.1: 0.5-alt1.1

Group :: Development/Other
Source RPM: arch-pqm

 Main   Changelog   Spec   Patches   Sources   Download   Gear   Bugs and FR (0/0)   Repocop 

Current version: 0.5-alt1.1.1.1
Built: over 6 years ago
Size: 72 KB
Repocop status: info

Home page:

License: GPL
Summary: arch patch queue manager

The idea is simple. You have a project with a number of developers. With a
revision control system like CVS, it's obvious that the project code will be
kept in a single repository, which all the developers use. You really don't
have much of a choice.

But arch is fully distributed. You want to take advantage of those features,
allowing your developers to commit while disconnected (say while they are
travelling with a laptop), easily create their own temporary branches without
affecting the main repository, and more. To accomplish these things, each
developer needs to have their own arch archive.

This then raises a question - where is the project? One solution is to pick a
specific developer to perform the task of merging in the other developer's
code. That developer's archive becomes the canonical one for the project.

However, there is a better way. The main idea of the tla patch queue manager is
to have a special archive which is managed entirely by the patch queue

Current maintainer: Alexey Voinov

List of contributors: ACL: List of rpms provided by this srpm:
  • arch-pqm
Recent changes (last three changelog entries):

2011-10-22 Vitaly Kuznetsov <vitty at> 0.5-alt1.1.1.1

    - Rebuild with Python-2.7

2009-11-16 Eugeny A. Rostovtsev (REAL) <real at> 0.5-alt1.1.1

    - Rebuilt with python 2.6

2008-01-24 Grigory Batalov <bga at> 0.5-alt1.1

    - Rebuilt with python-2.5.

© 2009–2018 Igor Zubkov