On Sunday, August 24, 2003, at 2:14 PM, Han The Man wrote:
>> > That was useful info! But I must disagree with the consensus "b)
>> redundant
>> > with existing 3rd-party tools" since there are no good/stable web
>> browsing
>> > facilities for Subversion around.
>>
>> What makes you think it would be easier to write entirely new
>> web-browsing functionality than it would be to make ViewCVS more
>> stable? I'm always mystified by the "foo doesn't work for me, so I
>> want
>> more options to be created" attitude.
>
> I didn't say it would be easier. But it would be easier for users just
> to install SVN and get browsing out of the box. And the fact is,
> ViewCVS doesn't work well with Subversion.
Let's separate the issues again.
1. ViewCVS doesn't work well with subversion
2. Subversion browsing out of the box doesn't do as much as you want.
Here's a radical idea:
If 1 is fixable, and a fixed ViewCVS does what you want, why don't we
just ship a future revision of ViewCVS that works well with Subversion
with Subversion in the contrib dir (just so people don't have to go and
grab Yet Another thing, but not configure it) or the tools dir (if we
feel like reusing the python configure support to handle ViewCVS
configuring too, and finding the right place to install it)th
It's not like ViewCVS goes through tons of releases, so it's likely not
something that requires all that much maintenance in the source tree.
If this isn't acceptable, Han, I suggest you write your own
subversion-only repository browser in python that does what you want,
and then submit it for the tools or contrib dir.
The fact is, while people are willing to fix ViewCVS bugs, nobody is
going to write a new browser for you, in or out of subversion.
You'd have to do it yourself.
--Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 25 07:10:15 2003