I've commited an updated ebuild for sys-fs/btrfs-progs-0.19_p111201 based on a discrete commit (using the EGIT_COMMIT="..." variable) from the upstream git repository at http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git
I wanted to document to the Sabayon development team why I've moved to a git based ebuild so you'll understand why it's there and when it makes sense to change back. First off, the movement towards an official 0.20 release is moving at a glacial pace. But there are many very important updates that have been published to the git repositories in the mean time. In the latest version, I've included the first generation of recovery tools to assist users in retrieving data from btrfs partitions that have been corrupted. Although a read/write btrfsck that can fix corruptions is not yet available, this is an important interim tool (I've heard it quipped that mkfs is the fsck for btrfs :) ) Also, since the hacking of the kernel.org servers in August/September of 2011, the official btrfs-progs-0.19 sources are no longer available. The sources are widely available on mirrors and in other distro's repositories, so that is only of minor relevance. As progress slowly moves towards the 0.20 version, I anticipate an extended period where all the update work will be scattered across various git repositories. So it will facilitate us in keeping up with updated features to structure the btrfs-progs ebuild from git sources until development settles down to a discrete release schedule.
