You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ma...@apache.org on 2012/03/13 15:30:22 UTC
svn commit: r1300147 - /subversion/site/publish/packages.html
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.
Modified:
subversion/site/publish/packages.html
Modified: subversion/site/publish/packages.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/packages.html?rev=1300147&r1=1300146&r2=1300147&view=diff
==============================================================================
--- subversion/site/publish/packages.html (original)
+++ subversion/site/publish/packages.html Tue Mar 13 14:30:22 2012
@@ -103,7 +103,7 @@
$ yum install mod_dav_svn</pre>
</li>
<li><p><a href="http://www.collab.net/downloads/subversion/redhat.html">
- CollabNet</a> (client only; supported and certified by
+ CollabNet</a> (supported and certified by
<a href="http://www.collab.net/subversion"
>CollabNet</a>; <i>requires registration</i>)</p>
</li>
@@ -299,7 +299,7 @@ $ pkg_add ap2-subversion</pre>
$ yum install mod_dav_svn</pre>
</li>
<li><p><a href="http://www.collab.net/downloads/subversion/redhat.html">
- CollabNet</a> (client only; supported and certified by
+ CollabNet</a> (supported and certified by
<a href="http://www.collab.net/subversion"
>CollabNet</a>; <i>requires registration</i>)</p>
</li>
@@ -334,7 +334,7 @@ $ yum install mod_dav_svn</pre>
<ul>
<li><p><a href="http://www.collab.net/downloads/subversion/solaris.html"
- >CollabNet</a> (client only; SPARC/x86; supported and certified by
+ >CollabNet</a> (SPARC/x86; supported and certified by
<a href="http://www.collab.net/subversion"
>CollabNet</a>; <i>requires registration</i>)</p>
</li>
@@ -363,7 +363,7 @@ $ yum install mod_dav_svn</pre>
<ul>
<li><p><a href="http://www.collab.net/downloads/subversion/redhat.html">
- CollabNet</a> (client only; supported and certified by
+ CollabNet</a> (supported and certified by
<a href="http://www.collab.net/subversion"
>CollabNet</a>; <i>requires registration</i>)</p>
</li>
@@ -422,7 +422,7 @@ $ apt-get install libapache2-svn</pre>
<ul>
<li><p><a href="http://www.collab.net/downloads/subversion/"
- >CollabNet</a> (client only; supported and certified by
+ >CollabNet</a> (supported and certified by
<a href="http://www.collab.net/subversion"
>CollabNet</a>; <i>requires registration</i>)</p>
</li>
Re: svn commit: r1300147 - /subversion/site/publish/packages.html
Posted by Mark Phippard <ma...@gmail.com>.
On Tue, Apr 17, 2012 at 1:57 PM, Mark Phippard <ma...@gmail.com> wrote:
> 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.
FWIW, the description of the package says: "Includes all Subversion
command-line binaries." which was my attempt to make this more clear.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Re: svn commit: r1300147 - /subversion/site/publish/packages.html
Posted by Mark Phippard <ma...@gmail.com>.
On Tue, Apr 17, 2012 at 1:48 PM, Greg Stein <gs...@gmail.com> wrote:
> On Tue, Mar 13, 2012 at 10:30, <ma...@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/
Re: svn commit: r1300147 - /subversion/site/publish/packages.html
Posted by Greg Stein <gs...@gmail.com>.
On Tue, Mar 13, 2012 at 10:30, <ma...@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?
Cheers,
-g