Difference between revisions of "Pacman Development"

From ArchWiki
Jump to: navigation, search
(Developer Repositories: add a few more)
(External References and Links: update/refresh links)
Line 8: Line 8:
  
 
* [http://archlinux.org/pacman/ Pacman Homepage]
 
* [http://archlinux.org/pacman/ Pacman Homepage]
* [http://projects.archlinux.org/?p=pacman.git;a=blob_plain;f=NEWS;hb=HEAD Latest NEWS/ChangeLog]
+
* [http://projects.archlinux.org/pacman.git/plain/NEWS?id=HEAD Latest NEWS/ChangeLog]
* [http://projects.archlinux.org/?p=pacman.git Pacman Gitweb]
+
* [http://projects.archlinux.org/pacman.git/ Pacman Git Web Interface]
* [http://www.archlinux.org/pipermail/pacman-dev/ Mailing List Archives]
+
* [http://mailman.archlinux.org/pipermail/pacman-dev/ Mailing List Archives]
 
* [http://www.nabble.com/pacman-dev-f16443.html ML Archives with search engine]
 
* [http://www.nabble.com/pacman-dev-f16443.html ML Archives with search engine]
 
* [http://archlinux.org/pacman/HACKING.html HACKING]
 
* [http://archlinux.org/pacman/HACKING.html HACKING]
 
* [http://archlinux.org/pacman/submitting-patches.html Submitting Patches]
 
* [http://archlinux.org/pacman/submitting-patches.html Submitting Patches]
 
* [http://archlinux.org/pacman/translation-help.html Translation Help]
 
* [http://archlinux.org/pacman/translation-help.html Translation Help]
 
* [http://toofishes.net/blog/git-workflow-pacman/ Git workflow with pacman]
 
* [http://toofishes.net/blog/using-valgrind-c-programming/ Using valgrind for C programming]
 
* [http://toofishes.net/blog/using-gcov-code-coverage-testing/ Using gcov for code coverage testing]
 
* [http://toofishes.net/blog/valgrind-330-and-new-massif/ Valgrind 3.3.0 and the new massif]
 
  
 
==Developer Repositories==
 
==Developer Repositories==

Revision as of 16:19, 14 June 2011

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:Pacman Development#)

Interested in Pacman Development? This page should help you get started.

Remember that if you think something belongs on this page, add it! The current pacman developers are not likely to know what people need to know and should be on this page.

External References and Links

Developer Repositories

A handful of the "regulars" have their own repositories with work in progress, working and feature branches, etc. Several are listed here, but feel free to add more that you may know about.

Allan McRae

Web: http://projects.archlinux.org/users/allan/pacman.git/
Clone: git://projects.archlinux.org/users/allan/pacman.git
Clone: http://projects.archlinux.org/git/users/allan/pacman.git

Dan McGee

Web: http://code.toofishes.net/cgit/dan/pacman.git/
Clone: git://code.toofishes.net/dan/pacman.git
Clone: http://code.toofishes.net/git/dan/pacman.git

Dave Reisner

Web: https://github.com/falconindy/pacman
Clone: git://github.com/falconindy/pacman.git
Clone: https://github.com/falconindy/pacman.git

Nagy Gabor

Web: http://repo.or.cz/w/pacman-ng.git
Clone: git://repo.or.cz/pacman-ng.git
Clone: http://repo.or.cz/r/pacman-ng.git

Xavier Chantry

Web: http://code.toofishes.net/cgit/xavier/pacman.git/
Clone: git://code.toofishes.net/xavier/pacman.git
Clone: http://code.toofishes.net/git/xavier/pacman.git

GIT Cheat Sheet

Before using the git cheat sheet, it is highly recommended to read the Super_Quick_Git_Guide

Clone git repo - only needed once

 git clone git://projects.archlinux.org/pacman.git pacman

Enable useful hooks

 chmod +x .git/hooks/{applypatch-msg,commit-msg,pre-commit,pre-rebase}

Create branch "<branch>"

 git branch <branch>

Work with branch "<branch>"

 git checkout <branch>

Commit changes on current branch and make patch to master branch

 git commit -a -s
 git format-patch master

Amend patch (Don't use it after a push)

 git commit -a --amend -s

Add file "<file>"

 git add <file>

Remove file "<file>"

 git rm <file>

Remove branch "<branch>"

 git branch -D <branch>

Update master branch

 git checkout master
 git pull

Merge changes on master with "<branch>"

 git rebase master <branch>

Get maint branch

 git branch -r
 git checkout -b maint origin/maint

Add a remote repository

  git remote add toofishes http://code.toofishes.net/gitprojects/pacman.git

Get toofishes working branch

  git branch -r
  git checkout -b toofishes-working toofishes/working