> Reading the kdump output, I see it loads
> /usr/pkg/share/tuxtype2/data/images/standby.png
> and then /usr/pkg/share/tuxtype2/data/sounds/tock.wav, then
> /usr/pkg/share/tuxtype2/data/sounds/pop.wav and others. (It seems wrong
> that it looks in other directories first though.)
Actually, the default behavior from tuxtype1 (and I guess it's still doing
this in tuxtype2, though I've not checked myself) was to run through a
series of possible locations when trying to load each file. This was great
for tuxtype1 which had a buggy auto{conf|make} setup.
Ultimately, for tt2, I would think (and Jesse, correct me if I'm wrong)
that it would only need to check two places:
1) {SOME_INSTALL_PATH_DETERMINED_BY_MAKEFILES}/data... etc.
2) ./data... etc.
You still want to keep the second fall back search path for a) developers
who want to test it without installing it and b) for some OSes like
Windows, etc.
However, all the other places to check are probably legacy kruft that
could be yoinked.
> It appears the problems start here:
<snip>
> I don't see any of those .png files.
>
> Anyone using tuxtype2-1.5.0 under NetBSD?
>
> Any ideas?
Someone was trying to make it work under FreeBSD, if that helps. Are they
still on this list?
> Also, is there such thing as Tuxtype 1.5.0? Should I have the package
> named "tuxtype-1.5.0" or "tuxtype2-1.50"? Is there any reason for me to
> name it tuxtype2 instead of tuxtype?
I would say yes, name it tuxtype2. tuxtype == tuxtype 1, and is very
different from tuxtype2. Eventually, I'd like to just retire tuxtype 1,
but for now, I elect we just say tuxtype2 is a pseudo-sequel ;-)
--
Sam Hart
University/Work addr. <[EMAIL PROTECTED]>
Personal addr. <[EMAIL PROTECTED]>
Alternative <[EMAIL PROTECTED]>
end
_______________________________________________
Tuxtype-dev mailing list
[EMAIL PROTECTED]
http://tux4kids.net/mailman/listinfo/tuxtype-dev
