summaryrefslogtreecommitdiff
blob: 3def14ae182bdac8be7466858ca1c68a8a2eb346 (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 gnome-base/libghttp
# Copyright 2002-2003 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/gnome-base/libghttp/ChangeLog,v 1.14 2003/10/28 00:59:32 brad_mssw Exp $

  27 Oct 2003; Brad House <brad_mssw@gentoo.org> libghttp-1.0.9-r3.ebuild:
  add amd64 flag

*libghttp-1.0.9-r3 (24 Jan 2003)

  06 Jul 2003; Guy Martin <gmsoft@gentoo.org> libghttp-1.0.9-r3.ebuild :
  Added hppa to KEYWORDS.

  30 Mar 2003; foser <foser@gentoo.org> libghttp-1.0.9-r3.ebuild :
  streamlined it a bit (use econf/einstall)

  25 Mar 2003; Aron Griffis <agriffis@gentoo.org> libghttp-1.0.9-r3.ebuild:
  Add ~alpha to KEYWORDS

  09 Mar 2003; Aron Griffis <agriffis@gentoo.org> libghttp-1.0.9-r3.ebuild:
  Mark stable on alpha

  07 Feb 2003; Aron Griffis <agriffis@gentoo.org> libghttp-1.0.9-r3.ebuild :
  Add ~alpha to KEYWORDS

  24 Jan 2003; foser <foser@gentoo.org> libghttp-1.0.9-r3.ebuild :
  Now copies extra headers needed for intermezzo (#11501)
  Now uses gnome.org eclass, fixed LICENSE

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
  12 Aug 2002; Mark Guertin <gerk@gentoo.org> libghttp-1.0.9-r2.ebuild :
  Added ppc to keywords

  09 Jun 2002; Martin Schlemmer <azarah@gentoo.org> libghttp-1.0.9-r2 :

  Libtoolized this one, as I had problems which libtoolize fixed with
  new install.

*libghttp-1.0.9-r2 (21 Mar 2002)

  21 Mar 2002; Seemant Kulleen <seemant@gentoo.org> libghttp-1.0.9-r2.ebuild :

  HTML documentation no longer gzipped.  Reported by: stefan@mdy.univie.ac.at 

*libghttp-1.0.9-r1 (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.