You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by bruce <be...@earthlink.net> on 2004/09/21 18:17:10 UTC
web interface to subversion... (websvn/pear/svn)
hi...
i'm reviewing websvn and the php-pear/svn libs as i'm going to need a way to
provide some basic web interaction with a svn repository.
i'm inclined to go towards using svnlook with the web app having direct
access to the repository. however, in looking at websvn/pear, it appears
that websvn provides direct svnlook hooks, whereas the pear/svn lib only
deals with svn.
i need to be able to do/provide the following types of interations with svn:
svn functions
return list of version numbers for a give file name
create/add/update/commit a dir based on a given dir name
create/add/update/commit a file based on a given file name
generate a list of files for a given dir
generate a list of dirs for a given parent dir
add new dir/file to svn access file for new dir/file
add new user to svn access file for given dir/file
based on this, does anybody have experience with either/both packages/apps
who can share with me your thoughts/comments on which app might make sense.
the major downside i see to the websvn app is that it's template based, and
if i rip it apart, i'm going to have to spend a good deal of time to
understand/modify the template mechanism to incorporate the requisite parts
into my app...
thoughts/comments/opinions/etc... are helpful...
thanks...
-bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: web interface to subversion... (websvn/pear/svn)
Posted by Max Bowsher <ma...@ukf.net>.
Peter Valdemar Mørch wrote:
> kfogel-at-collab.net |Lists| wrote:
>> Conflict detection is server-side; conflict *resolution* is
>> client-side.
>
> But if the client can't reliably know what version the
> about-to-be-checked-in version was based on and always tells the server
> that it is based on HEAD, haven't I then removed the ability of the
> server to do conflict detection?
Yes.
What you should do is remember what the base version was. Use a cookie or a
hidden form field. Then tell the server when you come to do a commit.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: web interface to subversion... (websvn/pear/svn)
Posted by Peter Valdemar Mørch <sw...@sneakemail.com>.
kfogel-at-collab.net |Lists| wrote:
> Conflict detection is server-side; conflict *resolution* is
> client-side.
But if the client can't reliably know what version the
about-to-be-checked-in version was based on and always tells the server
that it is based on HEAD, haven't I then removed the ability of the
server to do conflict detection?
My plan is to support locks once they are present in svn, and require
users to lock/modify/ci. But through the web interface, I can't really
know that the user modified the same version he locked... I *think* this
was Tim's beef with the whole web-write-access idea. It is a valid
point, just not one that is relevant in the particular use cases that I
have in mind.
Peter
--
Peter Valdemar Mørch
http://www.morch.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: web interface to subversion... (websvn/pear/svn)
Posted by kf...@collab.net.
Peter Valdemar Mørch <pe...@morch.com> writes:
> The lead developer of WebSVN, Tim Armes, and I disagreed in principle
> about whether it is a sane idea to provide commit access without a
> working copy directory and hence conflict detection, and so the code is
> probably never going to be part of stock-WebSVN.
Conflict detection is server-side; conflict *resolution* is
client-side.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: web interface to subversion... (websvn/pear/svn)
Posted by Peter Valdemar Mørch <pe...@morch.com>.
bruce bedouglas-at-earthlink.net |Lists| wrote:
> i'm going to need a way to
> provide some basic web interaction with a svn repository.
...
> based on this, does anybody have experience with either/both packages/apps
> who can share with me your thoughts/comments on which app might make sense.
About a month ago I developed a alfa for a "write"
(commit/add/delete/rename) enhancement/patch to WebSVN.
The lead developer of WebSVN, Tim Armes, and I disagreed in principle
about whether it is a sane idea to provide commit access without a
working copy directory and hence conflict detection, and so the code is
probably never going to be part of stock-WebSVN.
But at least you can find the beginnings of what you are looking for here:
http://morch.com/websvn/write/listing.php?repname=WebSVN&path=%2Fbranches%2Fwrite%2F
or equivalently here:
http://tinyurl.com/4cq2w
(I don't export my repository directly yet, sorry - You'll have to make
a tarball from the WebSVN interface yourself.)
I've discovered svk and so now I'll set up a repository that mirrors the
"original" WebSVN so I can keep up with it. But I haven't gotten there
yet. My version is up to date with
http://svn.collab.net/repos/websvn/trunk version 284.
> the major downside i see to the websvn app is that it's template based, and
> if i rip it apart, i'm going to have to spend a good deal of time to
> understand/modify the template mechanism to incorporate the requisite parts
> into my app...
I wasn't bogged down by that in the slightest. Actually I thought it
made for neater code all round. My $0.02.
Peter
--
Peter Valdemar Mørch
http://www.morch.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: web interface to subversion... (websvn/pear/svn)
Posted by bruce <be...@earthlink.net>.
clay,
thanks for the response...
is it possible i can give you a call to discuss what i'm doing, to see if
there might be an easier/more efficient way??
thanks
-bruce
bedouglas@earthlink.net
(925) 866-2790
-----Original Message-----
From: Clay Loveless [mailto:clay@killersoft.com]
Sent: Tuesday, September 21, 2004 1:06 PM
To: SVN-Users
Subject: Re: web interface to subversion... (websvn/pear/svn)
Hi Bruce,
As the author of the VersionControl_SVN package in PEAR, I can say that the
PEAR package does all of the things you listed below.
In fact, there are examples for each subclass that demonstrate each of the
tasks you listed.
WebSVN uses svnlook, which means you're out of luck for altering the
repository unless you hack in some of your own code.
VersionControl_SVN, on the other hand, will let you do everything you need
to do.
Take a look through the examples in the API documentation, and I believe
you'll find that the examples within will have you pretty far down the road
on what you need to accomplish.
-Clay
Example of repository listing with DHTML directory structure:
http://www.killersoft.com/packages/VersionControl_SVN.php
API docs:
http://www.killersoft.com/packages/VersionControl_SVN_docs/index.html
--
Killersoft.com
> From: bruce <be...@earthlink.net>
> Reply-To: <be...@earthlink.net>
> Date: Tue, 21 Sep 2004 11:17:10 -0700
> To: 'Subversion Users Mailing List' <us...@subversion.tigris.org>
> Subject: web interface to subversion... (websvn/pear/svn)
>
> hi...
>
> i'm reviewing websvn and the php-pear/svn libs as i'm going to need a way
to
> provide some basic web interaction with a svn repository.
>
> i'm inclined to go towards using svnlook with the web app having direct
> access to the repository. however, in looking at websvn/pear, it appears
> that websvn provides direct svnlook hooks, whereas the pear/svn lib only
> deals with svn.
>
> i need to be able to do/provide the following types of interations with
svn:
> svn functions
> return list of version numbers for a give file name
> create/add/update/commit a dir based on a given dir name
> create/add/update/commit a file based on a given file name
> generate a list of files for a given dir
> generate a list of dirs for a given parent dir
> add new dir/file to svn access file for new dir/file
> add new user to svn access file for given dir/file
>
> based on this, does anybody have experience with either/both packages/apps
> who can share with me your thoughts/comments on which app might make
sense.
> the major downside i see to the websvn app is that it's template based,
and
> if i rip it apart, i'm going to have to spend a good deal of time to
> understand/modify the template mechanism to incorporate the requisite
parts
> into my app...
>
> thoughts/comments/opinions/etc... are helpful...
>
> thanks...
>
> -bruce
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: web interface to subversion... (websvn/pear/svn)
Posted by Clay Loveless <cl...@killersoft.com>.
Hi Bruce,
As the author of the VersionControl_SVN package in PEAR, I can say that the
PEAR package does all of the things you listed below.
In fact, there are examples for each subclass that demonstrate each of the
tasks you listed.
WebSVN uses svnlook, which means you're out of luck for altering the
repository unless you hack in some of your own code.
VersionControl_SVN, on the other hand, will let you do everything you need
to do.
Take a look through the examples in the API documentation, and I believe
you'll find that the examples within will have you pretty far down the road
on what you need to accomplish.
-Clay
Example of repository listing with DHTML directory structure:
http://www.killersoft.com/packages/VersionControl_SVN.php
API docs:
http://www.killersoft.com/packages/VersionControl_SVN_docs/index.html
--
Killersoft.com
> From: bruce <be...@earthlink.net>
> Reply-To: <be...@earthlink.net>
> Date: Tue, 21 Sep 2004 11:17:10 -0700
> To: 'Subversion Users Mailing List' <us...@subversion.tigris.org>
> Subject: web interface to subversion... (websvn/pear/svn)
>
> hi...
>
> i'm reviewing websvn and the php-pear/svn libs as i'm going to need a way to
> provide some basic web interaction with a svn repository.
>
> i'm inclined to go towards using svnlook with the web app having direct
> access to the repository. however, in looking at websvn/pear, it appears
> that websvn provides direct svnlook hooks, whereas the pear/svn lib only
> deals with svn.
>
> i need to be able to do/provide the following types of interations with svn:
> svn functions
> return list of version numbers for a give file name
> create/add/update/commit a dir based on a given dir name
> create/add/update/commit a file based on a given file name
> generate a list of files for a given dir
> generate a list of dirs for a given parent dir
> add new dir/file to svn access file for new dir/file
> add new user to svn access file for given dir/file
>
> based on this, does anybody have experience with either/both packages/apps
> who can share with me your thoughts/comments on which app might make sense.
> the major downside i see to the websvn app is that it's template based, and
> if i rip it apart, i'm going to have to spend a good deal of time to
> understand/modify the template mechanism to incorporate the requisite parts
> into my app...
>
> thoughts/comments/opinions/etc... are helpful...
>
> thanks...
>
> -bruce
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org