# ChangeLog for net-misc/snarf # Copyright 2002-2007 Gentoo Foundation; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/net-misc/snarf/ChangeLog,v 1.20 2007/02/10 02:54:29 beandog Exp $ 10 Feb 2007; Steve Dibb snarf-7.0-r2.ebuild: amd64 stable, bug 165534 23 Dec 2006; Piotr JaroszyƄski snarf-7.0-r2.ebuild: Add ~amd64 wrt bug #157276. 01 Jul 2004; Jon Hood snarf-7.0-r2.ebuild: change virtual/glibc to virtual/libc, add IUSE 26 Apr 2004; Tavis Ormandy snarf-7.0-r2.ebuild: updated description, fixing #49055 25 Mar 2004; Jason Wever snarf-7.0-r2.ebuild: Stable on sparc. 19 Mar 2004; Jason Wever snarf-7.0-r2.ebuild: Added ~sparc keyword. 24 Oct 2003; Tavis Ormandy snarf-7.0-r2.ebuild: src_compile isnt required. using virtual/glibc, instead of >=sys-libs/glibc-2.1.3 `into` command not required. 20 Oct 2003; Tavis Ormandy snarf-7.0-r2.ebuild: s/make/emake/ 20 Oct 2003; Tavis Ormandy snarf-7.0-r2.ebuild: adding a postinst blurb with commands to enable snarf for portage downloading. 20 Oct 2003; Tavis Ormandy snarf-7.0-r2.ebuild: marking stable. *snarf-7.0-r2 (01 Aug 2003) 01 Aug 2003; Tavis Ormandy snarf-7.0-r2.ebuild, files/snarf-basename-patch.diff, files/snarf-unlink-empty.diff: Adding a new ebuild that contains two new patches i've created, a patch that unlinks empty files (essential for developer use with snarf as a FETCHCOMMAND), and a patch that adds a -b/-B option to only display the basename of the output, useful for use with FETCHCOMMAND. Setting myself as Maintainer, as gbevin has retired. 06 Dec 2002; Rodney Rees : changed sparc ~sparc keywords *snarf-7.0-r1 (30 Aug 2002) 16 Apr 2003; Tavis Ormandy snarf-7.0-r1.ebuild: Marking stable on alpha. 30 Aug 2002; Sasha Schwabbauer snarf-7.0-r1.ebuild : Added ppc to keywords. *snarf-7.0-r1 (1 Feb 2002) 09 Jul 2002; phoen][x snarf-7.0-r1.ebuild : Added KEYWORDS, LICENSE, SLOT. 1 Feb 2002; G.Bevin ChangeLog : Added initial ChangeLog which should be updated whenever the package is updated in any way. This changelog is targetted to users. This means that the comments should well explained and written in clean English. The details about writing correct changelogs are explained in the skel.ChangeLog file which you can find in the root directory of the portage repository.