final thoughts - bug tracking system

[Michel Talon]

flybsd.org> <43308ec0$0$740$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
User-Agent: KNode/0.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
Lines: 27
NNTP-Posting-Host: 134.157.10.41
X-Trace: 1127292804 crater_reader.dragonflybsd.org 740 134.157.10.41
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:9094

walt wrote:

> 
> So I just grep through the code for strings like 'FreeBSD' and 'NetBSD'
> and try to figure out how I can teach 'config' to recognize problems
> which are specific for DragonFly.  I'm hoping that Geert has kept a
> record of all the fixes I've emailed him so far.  Most of the fixes
> are truly trivial -- only one took a bit of head-scratching.

In my case (on FreeBSD) the build exploded when compiling the code
for font management. Hence i had the occasion to take a look at it
and see that it is an enormous block of c++ code dealing with all
sorts of details like hinting of fonts. When you see that, you understand
the grandiosity of Java project, they build a whole self consistent
world, but they use the vast richness of c++ syntax, and this
can be hairy! Anyways, i succeeded to tweak the code (i suppose 
font management would have been buggy after that!) and get the thing to
compile to the end. Anyways with patchset 2 i had exactly zero problem.

To come back to Dragonfly, i think one of the big problems of the Java
port to FreeBSD has been the threading library, and i think that
Dfly has more or less the same as Free, the D. Xu library, so it
should work with no big problem, i suppose.


-- 
Michel Talon