Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
podcatching client based on BashPodder
Fetching latest commit…
Cannot retrieve the latest commit at this time.
|Type||Name||Latest commit message||Commit time|
|Failed to load latest commit information.|
mashpodder podcatching client based on BashPodder UPDATE 2015: I am no longer maintaining mashpodder. Starting in 2005, I have maintained a 'user-contributed' version of BashPodder, the great podcatcher originally written by Linc Fessenden. My mashup has become pretty popular, and I have maintained five separate releases since that time. I ended up rewriting much of my original mashup and so when version 0.6 was ready, I decided to rename my version 'mashpodder' (as it is a mashup of BashPodder and other stuff) and put it on Google Code. I eventually moved it to GitHub. Mashpodder allows the user to download podcast episodes. The user can choose to save these episodes in a named directory (i.e. separate directory per feed) or in a date-based directory, so the most recent episodes are in one folder. Or, the user can combine this by having some podcasts in a named directory and others in the date-based directory. The user can choose to download all, none, or a set number of episodes per feed. The user can also choose to mark the episodes as downloaded (without actually downloading them) which can be used to 'catch up' to a podcast. Three files are needed: mashpodder.sh, mp.conf, and parse-enclosure.xsl. All three of these files are available here in the mashpodder repository. You can also browse through the source tree and download the files directly. There is also a sample cron wrapper script that folks can use and modify. I will occasionally package up a simple tarball of these files to make it easier for folks to download. Note, you also need wget, curl, and xsltproc installed. They are usually included in most default distro installs or you can get them from your distro's repositories. Finally, about the Git repo: this is a tiny project so there will only be one branch, which is 'master' and that will contain the latest code and patches and testing bits. It may or may not work at any given time. However, when it seems that the code is stable, I'll tag a release. So, basically, if you want something stable, use the latest release. If you want the latest-and-greatest or want to help test, use the master branch. Enjoy!