blob: 4637db792f8e365fd3cbb81791141f2418da96f6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
# ChangeLog for dev-util/cscope
# Copyright 2002-2003 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-util/cscope/ChangeLog,v 1.14 2003/11/15 18:29:15 jbms Exp $
15 Nov 2003; Jeremy Maitin-Shepard <jbms@gentoo.org> cscope-15.4-r1.ebuild:
Fixed emacs lisp and site file installation.
Problem and fix identified by Anupam Kapoor <anupamk@speakeasy.net>
15 Nov 2003; Arun Thomas <sindian@gentoo.org> cscope-15.4.ebuild:
added IUSE
20 Sep 2003; Matthew Kennedy <mkennedy@gentoo.org> cscope-15.4.ebuild:
adjust for elisp/elisp-common eclass split and corrent Changelog name
20 Sep 2003; Matthew Kennedy <mkennedy@gentoo.org> cscope-15.4.ebuild:
unmasking for ~x86 only.
19 Sep 2003; Seemant Kulleen <seemant@gentoo.org> cscope-15.3.ebuild,
cscope-15.4.ebuild:
added a fix for the compile to work with all versions of bison. This fix came
from the incomparable Brandy Westcott <brandy@gentoo.org> fixing bug #28755,
by Matt Kennedy <mkennedy@gentoo.org>
05 Jun 2003; Will Woods <wwoods@gentoo.org> cscope-15.3.ebuild,
cscope-15.4.ebuild:
added gnuconfig_update to fix ./configure on newer arches
*cscope-15.4 (04 Jun 2003)
04 Jun 2003; Matthew Kennedy <mkennedy@gentoo.org> cscope-15.4.ebuild,
files/50xcscope-gentoo.el:
minor version bump and support for emacs
08 Feb 2003; Guy Martin <gmsoft@gentoo.org> cscope-15.3.ebuild :
Added hppa to keywords.
06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
*cscope-15.3 (1 Feb 2002)
24 Feb 2003; Zach Welch <zwelch@gentoo.org> cscope-15.3.ebuild :
Add arm keyword
09 Feb 2003; Jan Seidel <tuxus@gentoo.org>
Added mips to keywords :
1 Feb 2002; G.Bevin <gbevin@gentoo.org> 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.
|