>>>>> On Sat, 9 Apr 2016, Lars Wendler wrote: >>> > Yes, I still use these lines to check for ebuild changes between >>> > portage and my personal overlay. So please keep this line.
> Enable the ident feature for *.ebuild files in git: > $ cat ~/gentoo/.git/info/attributes > *.ebuild ident > Now re-checkout every ebuild you wanna track. > $ git checkout -- > ~/gentoo/www-client/seamonkey/seamonkey-2.40.ebuild > Once you have done that those ebuilds will have some hash in the > $Id$ field: > $ grep '$Id' ~/gentoo/www-client/seamonkey/seamonkey-2.40.ebuild > # $Id: 5ecd7709c6c8a316d9f005b4e4a0a54da81eb048 $ > The same hash is in each corresponding ebuild in my personal overlay > as well. Occasionally I run a script to compare ebuilds from my > overlay with the one from the git tree. When the hash is different > something in the gentoo ebuild has changed and I can decide if I > want to apply these changes to ebuilds in my overlay as well. Why would you need $Id$ feature for this? "git ls-files -s" gives you the hash of the blob as well, is more efficient than grep, and even works recursively on a directory tree. $ git ls-files -s -- www-client/seamonkey/seamonkey-2.40.ebuild 100644 5ecd7709c6c8a316d9f005b4e4a0a54da81eb048 0 www-client/seamonkey/seamonkey-2.40.ebuild Ulrich
pgpOFBY7awgmg.pgp
Description: PGP signature
