blob: 1d1e507f6f6302b70ae87d6332ef2e69d549e8fa (
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
57
58
59
|
# ChangeLog for dev-java/jad-bin
# Copyright 2002-2007 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-java/jad-bin/ChangeLog,v 1.8 2007/02/09 01:55:19 flameeyes Exp $
09 Feb 2007; Diego Pettenò <flameeyes@gentoo.org> ChangeLog:
Regenerate digest in Manifest2 format.
22 Apr 2005; Simon Stelling <blubb@gentoo.org> jad-bin-1.5.8e.ebuild:
stable on amd64
03 Nov 2004; Thomas Matthijs <axxo@gentoo.org> jad-bin-1.5.8e.ebuild:
depend on app-arch/unzip
05 Sep 2004; Sven Wegener <swegener@gentoo.org> :
Fixed ChangeLog header.
05 Aug 2004; Thomas Matthijs <axxo@gentoo.org> jad-bin-1.5.8e.ebuild:
fix homepage
05 Aug 2004; David Holm <dholm@gentoo.org> jad-bin-1.5.8e.ebuild:
Contains x86 binaries, -ppc (bug #59465).
03 Aug 2004; David Holm <dholm@gentoo.org> jad-bin-1.5.8e.ebuild:
Added to ~ppc.
*jad-bin-1.5.8e (30 Jul 2004)
30 Jul 2004; Thomas Matthijs <axxo@gentoo.org> +metadata.xml,
+jad-bin-1.5.8e.ebuild:
move dev-java/jad dev-java/jad-bin
18 Jul 2004; Daniel Ahlberg <aliz@gentoo.org> jad-1.5.8e.ebuild:
Adding amd64 keyword, closing #53875.
19 May 2004; Chris Aniszczyk <zx@gentoo.org> jad-1.5.8e.ebuild:
Marking stable on x86
*jad-1.5.8e (09 Mar 2004)
09 Mar 2004; Chris Aniszczyk <zx@gentoo.org> jad-1.5.8d.ebuild,
jad-1.5.8e.ebuild:
Version bump and clean up.
*jad-1.5.8d (13 Apr 2002)
01 Apr 2002; Karl Trygve Kalleberg <karltk@gentoo.org> jad-1.5.8d.ebuild :
Added LICENSE, SLOT and KEYWORDS. Note: The package doesn't include a proper
license, and is assumed to be "Freely Distributable".
13 Apr 2002; Karl Trygve Kalleberg <karltk@gentoo.org> jad-1.5.8d.ebuild files/digest-jad-1.5.8d :
Jad is a Java decompiler, i.e. program that reads one or more Java class
files and converts them into Java source files which can be compiled again.
Jad is a 100% pure C++ program and it generally works several times faster
than decompilers written in Java. Jad doesn't use the Java runtime for its
functioning, therefore no special setup is required (like changes to the
CLASSPATH variable).
|