Gentoo Archives: gentoo-dev

From: Karl Trygve Kalleberg <karltk@×××××××.no>
To: gentoo-dev@g.o
Subject: Re: [gentoo-dev] best practices for java ebuilds
Date: Tue, 05 Feb 2002 09:39:06
Message-Id: Pine.LNX.3.96.1020205163139.3072J-100000@pluto.prosalg.no
In Reply to: [gentoo-dev] best practices for java ebuilds by Matthew Kennedy
1 We want to compile from sources always, because:
2
3 1) The user might want to tweak the source code before compiling
4 2) The user might want to apply a third-party patch
5 3) The binary packages supplied by the authors do not always contain
6 the javadoc documentation
7 4) We like source code :)
8
9 There is also a point to be made about consistency: In general, the user
10 should be able to assume that when using an ebuild, the system will
11 automatically obtain the source code for him. We are (slowly) working on
12 binary packages for all ebuilds, so when users are 100% certain they do
13 not want to spend time compiling from the sources, they can install the
14 binary packages instead. In this case, it would be a bit peculiar if
15 binary-only was available in the source-only tree, too, and no sources
16 were available.
17
18 So in short: We try hard (but not hard enough, as evidenced by the
19 tomcat-4.0.1 ebuild) to compile all Java packages from sources. Any
20 package that does not, should be considered faulty, and a bug report
21 should be filed.
22
23
24 Kind regards,
25
26 Karl T