[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r1300147 - /subversion/site/publish/packages.html

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 17 Apr 2012 13:57:16 -0400

On Tue, Apr 17, 2012 at 1:48 PM, Greg Stein <gstein_at_gmail.com> wrote:
> On Tue, Mar 13, 2012 at 10:30,  <markphip_at_apache.org> wrote:
>> Author: markphip
>> Date: Tue Mar 13 14:30:22 2012
>> New Revision: 1300147
>>
>> URL: http://svn.apache.org/viewvc?rev=1300147&view=rev
>> Log:
>> * publish/packages.html
>>  (centos, redhat, solaris, suse, windows) Removed client-only designation from CollabNet downloads.
>>  Package now includes all of the SVN binaries.  Only Apache + mod_dav_svn are in a separate package.
>
> On the target pages, I only see Edge. No "vanilla" server. I thought
> we had agreed that the landing pages required vanilla client and/or
> server in order to be listed as client/server on our packages.html
> page? Having larger vendor packages on the landing page was deemed
> "fine", as long as vanilla was present. Given that the landing pages
> don't have vanilla servers, then it seems packages.html should still
> state "client only".
>
> Maybe they had vanilla at the time of this change, but have been
> dropped at some point?

I think it might just be terminology. What you are calling vanilla is
called "command-line client". It includes everything in the build of
SVN, all binaries, except mod_dav_svn. It includes svnadmin,
svnserve, svnsync, the tools etc... We could include mod_dav_svn but
since we build with the latest Apache it would not work with the one
provide by a Linux distro anyway. So we do not include it in the
package.

I am not against improving the label on that page. It was already
called command line client and I could not think of anything better.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2012-04-17 19:57:50 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.