Quote:
|
Originally Posted by bluetoad Kevin, I don't want to sound off at you because you seem very helpful in the forums. The product looks very promising.
But is that the source that your team are working from or have they ever built it? I would have filled up the bug system. I don't believe someone would leave so much broken stuff checked in for 14 days or whatever. |
We have in internal copy of the code we develop on and check-in each change. The CVS instance we expose is a sync'd replica. At times the sync gets behind but in general is should be up-to-date. You don't have to file a bug for *each* problem. If they seem like real issues you can group several into a single bug report if needed.
Quote:
|
Originally Posted by bluetoad OK. The per-packaged binaries ar part of the build... I see that sort of thing referred to. Can you please point me to the correct place to retrieve those.
We would like to contribute back into the project.
But currently I am missing something. |
Like I said we don't ship or supply them. You must get them from their respective sources; most are listed in the cvs build how-to.