From: Katharina W. <wol...@fh...> - 2012-04-03 11:02:04
|
Hi Frank, thanks for your quick answer. I've tried everything I could find on the vufind-documentation and managed to do a successfull checkout into the vendor-directory and have indeed a subfolder .svn inside it. It seems the problems lie with the directories in between. So the question for me at the moment is: how can I teach subversion about my directory-structure? Or doesn't subversion know about it at all? On the other hand I'm not quite sure if I understand vendor-branching correctly (either in the vufind-documentation or in the book), but as far as I understand that would be the optimal solution for our project. It's frustating to understand the theory of things and get hung up on the practical side of things. :-( Kate Am 03.04.2012 12:28 schrieb Frank Morgner: > > Hey Katharina, > > do have read the documentation site on vufind. > > http://vufind.org/wiki/subversion > > Take a look at it. If you like to follow the code developement do a > checkout as described below "Initial checkout". > > svn co https://vufind.svn.sourceforge.net/svnroot/vufind/trunk > [your_directory] > > In my opinion it isn't so easy to get quickly into subversion. So first > try out the checkout and track the developments with svn status -u and > update your files with svn update [filename] commands you like. > > >I just get the error message that "vendor is not a working copy". > > Maybe you've already doing a successful svn command on that directory. > Give a list with hidden file parameter to see if you have an .svn > subfolder in it. SVN warns you if you want to merge different branches > not belonging together. > > Hope that will work for you. > > Cheers, > Frank > > > > Am 03.04.2012 12:03, schrieb Katharina Wolkwitz: >> Hi All, >> >> thanks to Demians tipp I've managed to create my first repository. >> >> /var/svn/vufind >> >> So far so good. >> >> But - as I wanted to have a connection between the original vufind-development >> and my local project, I've tried to use vendor-branching as described in "The >> svn-book" (O'Reilly). But I've encountered a few problems with that: >> >> 1. >> I'm not sure where to put the new directory vendor. The book speaks of " first, >> you create a top-level directory (such as /vendor) to hold the vendor >> branches." >> Does top-level in this context mean I should create the directory like this: >> >> /var/svn/vufind/vendor ??? >> >> 2. >> When I try to use the command >> >> vufind-t00:/var/svn/vufind/1.4 # svn import vendor >> https://vufind.svn.sourceforge.net/svnroot/vufind/trunk/ -m 'Import der ersten >> 1.4 Lieferung' >> >> I get asked for a root password, which I don't have, then next I get asked for a >> username, which I do not have either, so I cannot use import to get the data >> into my vendor-directory. >> >> My vendor-directory has the path /var/svn/vufind/1.4/vendor/ >> >> When I try an export into my vendor-direcory and then try >> "svn add vendor" I just get the error message that "vendor is not a working copy". >> If I try a checkout it get the message that "/var/svn/vufind/1.4 is not a >> working copy". >> >> How can I get subversion to recognize the paths? >> >> >> I hope someone here is used to working with svn and can help me. >> >> Kate >> >> ------------------------------------------------------------------------------ >> Better than sec? Nothing is better than sec when it comes to >> monitoring Big Data applications. Try Boundary one-second >> resolution app monitoring today. Free. >> http://p.sf.net/sfu/Boundary-dev2dev >> _______________________________________________ >> VuFind-General mailing list >> VuF...@li... >> https://lists.sourceforge.net/lists/listinfo/vufind-general >> > > -- Mit freundlichen Grüßen Katharina Wolkwitz Fachhochschule Südwestfalen Hochschulbibliothek Haldener Straße 182 58095 Hagen Tel.: 02331/9330-607 FAX: 02331/9330-608 |