Forums / Developer / Extension eZSVN ( PubSVN )

Extension eZSVN ( PubSVN )

Previous topic

Developer

Next topic

Author	Message
Björn Dieding@xrow.de	Tuesday 24 August 2004 2:52:56 pm /* eZSVN for eZ publish Copyright (C) 2004 xrow GbR, Hannover Germany This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. */ Developed by Björn Dieding ( bjoern@xrow.de ) State: Stable PubSVN: http://pubsvn.ez.no/viewcvs/community/trunk/extension/ezsvn/ Thread in forum: http://ez.no/community/forum/developer/extension_ezsvn_pubsvn Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Paul Forsyth	Wednesday 25 August 2004 6:47:46 am Hi Björn, Nice tool. I wrote wrappers for importing CVS entries as objects last year but the project stalled somewhat. Out of curiosity why are you checking in the svn binaries into pubsvn? Have you modified them? Given the complexity of subversion it might be better to force the user to install subversion themselves. paul
Björn Dieding@xrow.de	Wednesday 25 August 2004 7:19:33 am The reason for applying the binaries to the extension is that usually svn under linux uses dynamic link libraries.... you won't find a static build for download. The eZSVN has a static build. I just wanted to make sure that if I apply the extension to a installation that it will automaticly run and become useable. I also excluded things that are not needed by the "wrapper". By the way the extension is not ready yet. I will need some more time to complete it. Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/

Author

Message

Björn Dieding@xrow.de

Tuesday 24 August 2004 2:52:56 pm

/*
eZSVN for eZ publish
Copyright (C) 2004 xrow GbR, Hannover Germany

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
*/

Developed by
Björn Dieding ( bjoern@xrow.de )

State: Stable

PubSVN:
http://pubsvn.ez.no/viewcvs/community/trunk/extension/ezsvn/
Thread in forum:
http://ez.no/community/forum/developer/extension_ezsvn_pubsvn

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Paul Forsyth

Wednesday 25 August 2004 6:47:46 am

Hi Björn,

Nice tool. I wrote wrappers for importing CVS entries as objects last year but the project stalled somewhat.

Out of curiosity why are you checking in the svn binaries into pubsvn? Have you modified them? Given the complexity of subversion it might be better to force the user to install subversion themselves.

paul

Björn Dieding@xrow.de

Wednesday 25 August 2004 7:19:33 am

The reason for applying the binaries to the extension is that usually svn under linux uses dynamic link libraries.... you won't find a static build for download. The eZSVN has a static build.

I just wanted to make sure that if I apply the extension to a installation that it will automaticly run and become useable.

I also excluded things that are not needed by the "wrapper".

By the way the extension is not ready yet. I will need some more time to complete it.