summaryrefslogtreecommitdiff
blob: 688251620c0f7796c0b7ff9e026be37dd6a1f54a (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
54
55
56
# ChangeLog for games-simulation/lincity
# Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/games-simulation/lincity/ChangeLog,v 1.8 2004/10/20 02:05:00 mr_bones_ Exp $

  19 Oct 2004; Michael Sterrett <mr_bones_@gentoo.org>
  -files/lincity-1.11a-gcc3.patch, -lincity-1.12_pre53.ebuild:
  clean older ebuild

  01 Jul 2004; Jeremy Huddleston <eradicator@gentoo.org>
  lincity-1.12.0.ebuild, lincity-1.12_pre53.ebuild:
  virtual/glibc -> virtual/libc

  27 Mar 2004; Michael Sterrett <mr_bones_@gentoo.org> lincity-1.12.0.ebuild,
  lincity-1.12_pre53.ebuild:
  use || to say what we really mean in DEPEND

*lincity-1.12.0 (22 Jan 2004)

  22 Jan 2004; Michael Sterrett <mr_bones_@gentoo.org> lincity-1.12.0.ebuild:
  version bump

  12 Dec 2003; Jon Portnoy <avenj@gentoo.org> :
  AMD64 keywords.

*lincity-1.12_pre53 (13 Jul 2003)

  13 Jul 2003; Mike Frysinger <vapier@gentoo.org> :
  Version bumped to update to the new install process and fix
  the HOMEPAGE for #17434.

*lincity-1.11a-r1 (5 May 2002)

  01 Nov 2002; Jon Nall <nall@gentoo.org> lincity-1.11a-r1.ebuild :
  added PPC to KEYWORDS

  01 Oct 2002; Mike Frysinger <vapier@gentoo.org> lincity-1.11a-r1.ebuild lincity-1.11a-gcc3.patch lincity-1.11a-Makefile.diff :
  Deleted old patch and made a new one to address same issues and more ... #8448

  17 jul 2002; Jose Alberto Su�rez L�pez <bass@gentoo.org> lincity-1.11a-r1.ebuild :
  Added LICENSE, KEYWORDS.

  5 May 2002; B.Verwilst <verwilst@gentoo.org> ChangeLog :

  Fixed bug #2194, now installs fine with sandbox.
  when X in use, links xlincity to lincity, to keep standard startup 
  method

*lincity-1.11a (1 Feb 2002)

  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.