dev-libs/libmcrypt/ChangeLog


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
57
58
59
60
61
62
63
64
65

# ChangeLog for dev-libs/libmcrypt
# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL
# $Header: /var/cvsroot/gentoo-x86/dev-libs/libmcrypt/ChangeLog,v 1.12 2003/01/05 11:22:16 aliz Exp $

*libmcrypt-2.5.5 (05 Jan 2003)

  05 Jan 2003; Daniel Ahlberg <aliz@gentoo.org> :
  Security update.

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
*libmcrypt-2.5.1-r4 (1 Jul 2002)

  1 Jul 2002; Martin Schlemmer <azarah@gentoo.org> :

  Ok, officially bug #3940 is fixed with -r3, but r4 is just the
  final with cleanups, etc.  Thanks Jon.

*libmcrypt-2.5.1-r3 (30 Jun 2002)

  30 Jun 2002; Martin Schlemmer <azarah@gentoo.org> :

  Another stab at bug #3940.

*libmcrypt-2.5.1-r2 (24 Jun 2002)

  24 Jun 2002; Seemant Kulleen <seemant@gentoo.org>
  libmcrypt-2.5.1-r2.ebuild files/digest-libmcrypt-2.5.1-r2.ebuild :

  elibtoolize

*libmcrypt-2.5.1-r1 (21 Jun 2002)

  21 Jun 2002: Gabriele Giorgetti <stroke@gentoo.org> libmcrypt-2.5.1-r1.ebuild

  Applied patch submitted by Jon Nelson <jnelson@gentoo.org>. Fixes bug #3940


*libmcrypt-2.5.1 (17 Jun 2002)

  17 Jun 2002: Gabriele Giorgetti <stroke@gentoo.org> libmcrypt-2.5.1.ebuild :

  New version. (Removed --host=${CHOST} from ebuild.) (#3517)

*libmcrypt-2.5.0 (14 Jun 2002)

  14 Jun 2002: Gabriele Giorgetti <stroke@gentoo.org> libmcrypt-2.5.0.ebuild :

  New version ( masked for testing ).

*libmcrypt-2.4.19-r1 (5 May 2002)

  5 May 2002: Martin Schlemmer <azarah@gentoo.org> libmcrypt-2.4.19-r1.ebuild :

  Resolve bug #2276.  Add $Header: /var/cvsroot/gentoo-x86/dev-libs/libmcrypt/ChangeLog,v 1.12 2003/01/05 11:22:16 aliz Exp $.

*libmcrypt-2.4.19 (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.