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.eckhardt_at_dominolaser.com]
Enviada em: terça-feira, 14 de agosto de 2012 09:43
Para: users_at_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.
****************************************************************************
**********
Received on 2012-08-14 16:05:46 CEST