Applications for SVN.
Hi all, I'm installing some versions control system at work and I'd like to have so suggestions about it. We've decided to use SVN, but it will be nice having some web application that it will allow developers to create and manage their own projects. It will avoid svn commands manually execution for any new project we create. It will be perfect if there is some web server application which allows projects management, installed in same machine as svn server. Then, the developers could create and manage their projects from any machine by web browser. I really don't know if there is some software with this feature. I've looked for some, I found viewvc and svn-web-admin. You advice me use one of them or any other? I will appreciate your help. Leonardo
svn move directory will create a new revision for every file inside this directory?
Hi, The command below will create a new revision for directory SRC_REP_DIR? And for files inside this directory? Had a new revision too? "svn move SRC_REP_DIR DST_REP_DIR" Command above use repository not WC. Regards, Leo
Re: svn move directory will create a new revision for every file inside this directory?
Hi Bob, Thanks for you replay. I heve the structure below: DIR_A - Rev 1 > File_A - Rev 2 DIR_B - Rev 3 If I move DIR_A to inside DIR_B the structure will be as: DIR_B - Rev 3 >DIR_A - Rev 4 >> File_A - Rev 2 So, the directory has a new revision (Rev 4), but files inside this directory does not ( Rev 2). If i try to get this file from: - REV: 2 - PEGREV: 2 - Path: DIR_B/DIR_A/FILE_A svn show error, because this path is not valid in PEGREV 2. Regards, Leo 2010/6/10 Bob Archer : >> The command below will create a new revision for directory SRC_REP_DIR? >> And for files inside this directory? Had a new revision too? >> >> "svn move SRC_REP_DIR DST_REP_DIR" >> >> Command above use repository not WC. > > That command is going to basically going to be the same as: > > svn copy SRC_REP_DIR DST_REP_DIR > svn delete SRC_REP_DIR > > Yes... a new revision will be created. The new path will be in HEAD and the > old path will not be. > > BOb > >
Re: svn move directory will create a new revision for every file inside this directory?
Hi Bob, You have already answered my question. It does not create a new revision for files inside directory that was moved. So, if I want to get FILE_A in REV 2 from path /DIR_B/DIR_A/FILE_A, I must use PEGREV 4 Regards 2010/6/10 Bob Archer : >> Thanks for you replay. >> >> I heve the structure below: >> >> DIR_A - Rev 1 >> > File_A - Rev 2 >> DIR_B - Rev 3 >> >> If I move DIR_A to inside DIR_B the structure will be as: >> >> DIR_B - Rev 3 >> >DIR_A - Rev 4 >> >> File_A - Rev 2 >> >> So, the directory has a new revision (Rev 4), but files inside this >> directory does not ( Rev 2). >> >> If i try to get this file from: >> - REV: 2 >> - PEGREV: 2 >> - Path: DIR_B/DIR_A/FILE_A >> svn show error, because this path is not valid in PEGREV 2. >> >> Regards, >> Leo > > Yes... you are 100% correct. What is your question? > > I think you may be making the mistake of expecting the each file is > revisioned separately. That is not the case. In rev2-4 your File_A is the > same. however, in rev4 its path in the repo is different than in rev2. But, > I'm babbling without really knowing what your question is. Have you read the > first chapter of the doc redbook? > http://svnbook.red-bean.com/nightly/en/svn-book.html > > BOb > > >> >> >> >> 2010/6/10 Bob Archer : >> >> The command below will create a new revision for directory SRC_REP_DIR? >> >> And for files inside this directory? Had a new revision too? >> >> >> >> "svn move SRC_REP_DIR DST_REP_DIR" >> >> >> >> Command above use repository not WC. >> > >> > That command is going to basically going to be the same as: >> > >> > svn copy SRC_REP_DIR DST_REP_DIR >> > svn delete SRC_REP_DIR >> > >> > Yes... a new revision will be created. The new path will be in HEAD and >> the old path will not be. >> > >> > BOb >> > >> > >
Libraries and projects into SVN
Hello. We desire to insert some projects into SVN and we have now to deal with some witch uses the same library. The developers here said that we always actualize the last library in order to be compatible with the older ones. We have talked about it and we think we have to create an individual repository for the library and the developers should actualize it very often manually. I mean, every time someone wants to change some project, he must to check out the project version and the libraries versions required for it. After developing or correction, the developer must actualize the project and the libraries separated. My questions are: 1) Is that right? I mean, Is there any better other way to control versions of libraries used for several projects? 2) Is it possible in SVN to make it automatic ? In other words, when the developer actualize (commit, merge, etc...) some project, is it possible to actualize the libraries together? One of us said it's possible to do this in GIT using sub-repositories. Is it possible in SVN? If so, is there any tutorial or advices to do this? I'm already glad for answers. Regards, Leonardo
RES: Libraries and projects into SVN
Hi, The system here is a bit complex and I will try to explain it. We have two main projects (P1 and P2). They are compiled in separated environments, generating *.exe different files, but they use the same source code allocated into a module (M1), that contains some functionalities like file system, file transfer, etc. We have also one library (L1) with 80% of source code equivalent of P1, and it is compiled separated from P1, generating a L1.dll file. The library L1 is used by three other application projects (A1, A2 and A3). So, three main situations: 1) When source code from P1 changes module M1, the P2 must have access to it, and vice-versa. 2) When source code from P1 changes shared code from L1, the L1 source code must be actualized, and vice-versa. 3) When L1.dll changes, A1, A2 and A3 should automatically start to use the new L1 created. I'm still a bit lost here how to share the codes into SVN. I think I may create one repository to each one (P1, P2, M1, L1, A1, A2 and A3). The problem is doing all svn commands for each one. For example, If I will change L1, I must to check out P1 and M1 to compile it. Then, after changes, I must commit P1, M1 and L1, for source code and commit the L1.dll file for A1, A2 and A3. It's unlikelly doing this manually. In other hand, I also think it's unlikelly to create only one repository for all these projects. Finally, our system is a bit more complex than it, but the main structure is this. Thanks again for your suggestions. Regards Leonardo -Mensagem original- De: Ulrich Eckhardt [mailto:ulrich.eckha...@dominolaser.com] Enviada em: terça-feira, 14 de agosto de 2012 09:43 Para: users@subversion.apache.org Assunto: Re: Libraries and projects into SVN Am 14.08.2012 14:14, schrieb Leonardo Laface de Almeida: > We desire to insert some projects into SVN and we have now to deal with some > witch uses the same library. The developers here said that we always > actualize the last library in order to be compatible with the older ones. Okay, so there is a component (a library) that is shared between different projects, right? Or is it that you check in the compiled .DLLs or .LIBs separately to the source code? This question is very important because of the different implications and strategies for approaching it. Reading the rest of your mail also doesn't make it clear, so it is impossible to give you proper advise without you answering that part first. Note that what Peter suggested mostly deals with how to share the content between different projects using it and not so much with how to store it. In any case, svn:externals are a good tool but they are not always the right one. Greetings! Uli ** Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932 ** Visit our website at http://www.dominolaser.com ** Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden. E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht verantwortlich. **