summaryrefslogtreecommitdiff
blob: 7dba20625183ff9d0a310861b6068fef92611b78 (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 app-arch/unlzx
# Copyright 1999-2009 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/app-arch/unlzx/ChangeLog,v 1.19 2009/10/12 17:03:20 halcy0n Exp $

  12 Oct 2009; Mark Loeser <halcy0n@gentoo.org> unlzx-1.1.ebuild:
  QA fixes; unquoted variables

  23 Oct 2008; Diego Pettenò <flameeyes@gentoo.org> unlzx-1.1.ebuild:
  Respect LDFLAGS, respect CC.

  26 Jan 2008; Fabian Groffen <grobian@gentoo.org> unlzx-1.1.ebuild:
  Dropped ppc-macos keyword, see you in prefix

  21 Feb 2007; Piotr Jaroszyński <peper@gentoo.org> ChangeLog:
  Transition to Manifest2.

  17 Sep 2005; Fabian Groffen <grobian@gentoo.org> unlzx-1.1.ebuild:
  Marking ~ppc-macos (bug #105868)

  28 Dec 2004; Ciaran McCreesh <ciaranm@gentoo.org> :
  Change encoding to UTF-8 for GLEP 31 compliance

  07 Jun 2004; Daniel Black <dragonheart@gentoo.org> +metadata.xml,
  unlzx-1.1.ebuild:
  QA - IUSE fix

  04 May 2004; Bryan Østergaard <kloeri@gentoo.org> unlzx-1.1.ebuild:
  Stable on alpha.

  05 Jan 2004; Jon Portnoy <avenj@gentoo.org> unlzx-1.1.ebuild :
  AMD64 keywords.

  24 Nov 2003; Aron Griffis <agriffis@gentoo.org> unlzx-1.1.ebuild:
  Add ~alpha

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
*unlzx-1.1 (23 Feb 2002)

  07 Sep 2002; Seemant Kulleen <seemant@gentoo.org> unlzx-1.1.ebuild :

  LICENSE to freedist, thanks to: r.a.mercer@blueyonder.co.uk (Adam Mercer)
  in bug #7290.

  14 Aug 2002; Pieter Van den Abeele <pvdabeel@gentoo.org> :

  Added ppc keyword

  23 Feb 2002; T.Neidt <tod@gentoo.org> ChangeLog, unlzx-1.1.ebuild, digest-unlzx-1.1 :
 
  Initial commit. Unlzx decompresses Amiga LZX archives.
  Version 1.1 supports pipes.
  Thanks to Per Wigren for the contribution.
  Note: there is no version in the tarball name.
  Suggestion on how to handle this welcome.