"Jan Hendrik" <list.jan.hendrik_at_gmail.com> writes:
> what about this "certified" business? In my humble understanding
> before long any request on this list or other places which has a
> buggy smell will be put down until the poster confirms it with the
> binaries from CollabNet. Just because any binary, at Tigris or
> elsewhere, is, well, not certified and in such a manner official and
> could just be the buggy reason for any issue. I will gladly be
> proven wrong, in the long run ... For it seems like the Windows
> installer at Tigris already has become victim of CollabNet's binaries.
I didn't understand what you were trying to say above. Could you give a
concrete example?
We accept bug reports from any useful source. I have no idea what
you're referring to with the word "certified". Somebody somewhere may
be certifying something, but that's not the Subversion project's
concern, as long as they comply with our trademark policy
(http://subversion.org/legal/trademark-policy.html).
> Personally I can live quite well with DJH's binaries package (thanks
> to him for still providing them!) though from time to time I liked the
> installer to get a more recent version of the SVN book in CHM
> format, IMHO easier to handle and on resources than PDF, and
> more comfortable to use than HTML (e.g. index, search) as found
> at red-bean.com.
>
> What bothers me with the CollabNet binaries even more than the
> registration (and almost always registration is followed by spam of
> some sort) is them forcing the use of particular versions of Apache
> and Python and probably other stuff. But I don't want to change
> from the Python.org binaries to ActivePython, nor do I like being
> pressed into changing to Apache 2.2 at this time. Yet I don't need
> just the SVN client, I run a local repository ... That's what I get from
> both the CollabNet download & requirements pages and from
> comments on this very list, haven't had the time and inclination to
> give their binaries an actual test run - that is after a proper HDD
> clone to get back onto my feet in the suspected case of mungings
> with my Apache & Python setup.
>
>> The registration is their choice, because it's their server. It has
>> nothing to do with "open source", except in this sense: it's because
>> Subversion is open source that CollabNet (and you, and anyone else)
>> has the freedom to make and post binaries.
>
> Certainly. It's only unfortunate for us programmatic greenhorn
> users that on Windows one has to throw out 600 bucks or so for
> the required compiler and then the hassle with the compiling
> business only begins. At this price - and that for the regular
> updates following en suite - there are ready-to-use version control
> systems out there. And when they require registration I know quite
> well they do so to prevent me from using their stuff with four hands -
> and for selling me additional maintenance ...
All of these criticisms should be directed at CollabNet, not to the
Subversion project.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-08 18:34:59 CEST