Blame is an excellent tool for use with RCS that provides output similar to CVS's annotate command. The tool would be great for anybody who still has to use RCS for project management, and obviously that extends to legacy CVS managed repositories when you don't have CVS installed too. But we don't care about that... The *great* thing about blame is you can use it on your dispatch-conf managed files in /etc/config-archive. Then when something goes wrong with your configuration it is incredibly easy to spot where and when changes have happened. Blame is capable of annotating user-specified versions by either RCS revision, date, etc. Heavily trimmed example output: $ blame /etc/config-archive/etc/bash/bashrc Annotations for bashrc *************** 1.4 (root 07-Sep-06): # /etc/bash/bashrc 1.4 (root 07-Sep-06): # 1.1 (root 09-Jul-05): # This file is sourced by all *interactive* bash shells on startup, 1.1 (root 09-Jul-05): # including some apparently interactive shells such as scp and rcp 1.4 (root 07-Sep-06): # that can't tolerate any output. So make sure this doesn't display 1.4 (root 07-Sep-06): # anything or bad things will happen ! .. 1.1 (root 09-Jul-05): # instead of using /etc/DIR_COLORS. Try to use the external file 1.5 (root 30-Sep-06): # first to take advantage of user additions. Use internal bash 1.5 (root 30-Sep-06): # globbing instead of external grep binary. 1.1 (root 09-Jul-05): use_color=false 1.5 (root 30-Sep-06): safe_term=${TERM//[^[:alnum:]]/?} # sanitize TERM 1.2 (root 21-Jul-05): if [[ -f /etc/DIR_COLORS ]] ; then 1.5 (root 30-Sep-06): match_lhs=$(</etc/DIR_COLORS) I was hoping to have come up with a suggested category by now, but I've failed miserably. I guess with rcs already being in app-text, and this tool being close to zero use on binary files, app-text would be a good match for it too. Locally, I've just had it dumped in dev-util :/ Thanks, James
Created attachment 108440 [details] blame-1.3.1.ebuild
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Heuristics show that no Gentoo developer has commented on your ebuild. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
Created attachment 230783 [details] blame-1.3.1.ebuild Just fixes the missing quotes from $D, and updates the dev-vcs/rcs usage comment. FWIW, I still use this package and keep the ebuild in an overlay but I will not be submitting it for possible inclusion in sunrise. Anyone else who uses it, should obviously feel free to do so though ;)
