summaryrefslogtreecommitdiff
blob: 1bc791423cbe7df1a70e5555212053ed1f9acb2c (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
# ChangeLog for dev-perl/Module-Signature
# Copyright 1999-2006 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-perl/Module-Signature/ChangeLog,v 1.9 2006/06/24 19:23:44 mcummings Exp $

*Module-Signature-0.54 (24 Jun 2006)

  24 Jun 2006; Michael Cummings <mcummings@gentoo.org>
  +Module-Signature-0.54.ebuild:
  Version bump.

  13 Feb 2006; Michael Cummings <mcummings@gentoo.org>
  Module-Signature-0.44.ebuild, Module-Signature-0.51.ebuild:
  Virtuals for perl-core

  07 Feb 2006; <mcumming@gentoo.org> Module-Signature-0.44.ebuild,
  Module-Signature-0.51.ebuild:
  bug 121189, dup'd module in tree

  13 Jan 2006; Michael Cummings <mcummings@gentoo.org>
  Module-Signature-0.44.ebuild:
  Marking x86 stable

*Module-Signature-0.51 (13 Jan 2006)

  13 Jan 2006; Michael Cummings <mcummings@gentoo.org>
  +Module-Signature-0.51.ebuild:
  Version bump upstream

  25 May 2005; Michael Cummings <mcummings@gentoo.org>
  Module-Signature-0.44.ebuild:
  dev-perl/MIME-Base64 => perl-core/MIME-Base64 migration

  06 May 2005; Sven Wegener <swegener@gentoo.org>
  Module-Signature-0.44.ebuild:
  Removed * postfix from <, <=, >= and > dependencies.

  11 Apr 2005; Ferris McCormick <fmccor@gentoo.org>
  Module-Signature-0.44.ebuild:
  Remove ~sparc keyword because dev-perl/math-pari-2.010603 will not build,
  and it will not build because pari-2.1.6 does not build on sparc; See Bug
  87790 for explanation.

*Module-Signature-0.44 (11 Apr 2005)

  11 Apr 2005; Michael Cummings <mcummings@gentoo.org> +metadata.xml,
  +Module-Signature-0.44.ebuild:
  Bugs 88267,88354(ok, that one i created for this), and the one that brought it
  up first, 83789. Here's the sum up: we tell users to use cpan or g-cpan if a
  module isn't in the tree. Fine. But if they do that, they can end up with a
  Module::Signature install because it becoming a silent dep in a lot of places
  to confirm the security/validity of a module installation. At least this way
  we can A) provide an ebuild that we can track/fix and B) we have some minor
  influence in the sanity of their environment. This should override any already
  installed versions and be safe for future uses.