(No subject header)

[eternal at antelecom.net]

sorry if i came off a little caustic, but i figured that it
might be the only way to get a response, any response.  i've
been to the wine packages for bsd section of sourceforge,
and tried all of them.  none of them are complete packages
(and once the .tgz was broken! (missing EOF) no one knew,
because obviously (to me), no one tried to see if it worked
before posting it there), atleast according to pkg_add and
portupgrade.  it would seem that the contents file is
missing.  i dont expect everyone to use the platform that i
use, but if you say you develop for it, shouldnt you atleast
test on it rather than just assume it works?  i mean, not
even the packages work.  i've already expressed my
willingness to the maintainers (will not name names) to
document what needs to get it running on bsd, provided that
someone could just help me read the traceback from building
wine.  and that offer to help fell on deaf ears, so offering
to help didnt result in help either, much less instant help.


shaun


So, let's see:
>   1. Wine works on FreeBSD. In fact, we even provide
binaries:
>
	http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=77562
>      As I hope you can see, the lastest release is there.
> 
>   2. None of the Wine developers run *BSD. As a result,
you will end up
>      having problems from time to time. We try to help fix
them, but
>      unless the *BSD people help out, they will not get
fixed. So more
>      patches and less bitching would be greatly
appreciated.
> 
>   3. I hate to break it to you, but this is free software.
I'm not sure
>      what's common behaviour in the BSD camp, but here
calling the developers
>      liers will not result in instant help.