Running gPodder from Git

From gPodderWiki

Jump to: navigation, search

To run gPodder from its Git repository, you have to check out a working copy from the repository, and then run make test to start gPodder from the current directory.

Contents

[edit] Step 1: Dependencies

To get gPodder-Git working, you need to install Git. In Debian and Ubuntu, you can install this by running (as root or with sudo): 

aptitude install git-core

For other distributions, the package should be named equally (look for "git" or "git-core").

You will also need to install the dependencies listed on this page to get gPodder running.

[edit] Step 2: Check out a working copy

  1. Open up a X terminal (gnome-terminal, etc..)
  2. Change to your Desktop folder or some other folder where you usually keep source packages of software: cd ~/Desktop
  3. Check out a working copy from gPodder's Git repository: 
    git clone git://repo.or.cz/gpodder.git
  4. After the check out, you should now have a gpodder folder with the source in it. Change into it: cd gpodder
  5. You can now run gPodder from this working copy without interference from your locally-installed distribution package (you don't need to uninstall it, gPodder will only use the gPodder package from the working copy) with using make test. This will also enable debugging mode, so you will see debugging output in your terminal window.
  6. To test the CLI modes, run bin/gpodder --local --help in the working copy folder. The --local switch turns on running from inside the working copy.

[edit] Step 3: Updating from the repository

Every now and then, changes will be committed into the repository. You can update you local working copy to the latest revision by running git pull in your working copy.

[edit] How do I create a patch?

Alright, so you have a Git working copy checked out as described above and made some changes. Entering git status should give you a list of files that have changed or that Git doesn't yet know about. If you have added/removed a file, use git add/rm path/to/file.py to add/remove the file. Then, run git status again and see if everything is included. make clean can help you to get rid of temporary files.

If you think you have added all necessary files, enter git diff --color to get a list of changes. You can create a patch file after comitt: 

git format-patch origin/master

You can review this file with a text editor of your choice, and if you like the changes, send it to the mailing list. If the file is bigger than 10kB, please "gzip" it first.

If the file is too big, the mailing list software will complain and your message will not be posted to the list. If your patch is not trivial, and might need discussion, it would be a good idea to file the patch as a bug report on our bug tracker. You can then send a mail to the mailing list containing a link to the bug page. You can (and should) attach your patch to the bug. Thanks!

Retrieved from "http://wiki.gpodder.org/wiki/Running_gPodder_from_Git"
Personal tools