Arch is a really nifty revision control system. It's "whole-tree
changeset based" which means, roughly, that it can handle (with atomic
commits) file and directory adds, deletes, and renames cleanly, and
that it does branching simply and easily. Arch is also "distributed"
which means, for example that you can make arch branches of your own
from remote projects, even if you don't have write access to the
revision control archives for those projects.
This looks to be as close to an open source p4 replacement as one could
hope without being p4. I'll go so far as to suggest that if this SCM
was employed by the BSD crowd, merging changes between dragonfly (post
source repo reorog), NetBSD, and OpenBSD would be radically less painful.
It is very possible that the dragonfly fork may not have happened under
the arch SCM development methodology, but if it did, at the very least it
would be possible to incorporate dillion's reorg work in a single patch
set, no cvs admin repo surgery needed.
WWW: http://arch.fifthvision.net/bin/view
naming of MP3 and Ogg-Vorbis files. It automates the whole process of ripping
data from music compact discs (CD), the naming of the files, their converting
into MP3 or Ogg-Vorbis format and the labelling of the MP3 files with an ID3
tag. dekagen uses dialog for a user interface that is intended to be
"intuitive".
Music data is read from CDs using cdda2wav, cdparanoia, dagrab, or tosha, and
stored on your harddisk in wav-format. Note that this will have an excessive
need of disk space. After this, the wav-data is converted into MP3 format
using 8hz-mp3, bladeenc, l3enc, lame, mp3enc, or notlame, or into Ogg-Vorbis
format using oggenc. This will take a while. To avoid manual naming and
tagging for all the files, cda is used for CDDB lookups. To label the MP3
files with ID3 tags, id3ed, id3tag, id3tool, or mp3info, or the built-in
capabilities of some encoders (lame, notlame) are used. Ogg-Vorbis files can
be labelled with oggenc.
WWW: http://userpage.fu-berlin.de/~mbayer/tools/dekagen.html
