Hi,
Von: Leonardo Laface de Almeida [mailto:leona...@sweda.com.br]
>
> 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 al
On Tue, Aug 14, 2012 at 9:05 AM, Leonardo Laface de Almeida
wrote:
>
> 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,
hanks 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, s
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
On Tuesday, August 14, 2012 09:14:47 Leonardo Laface de Almeida wrote:
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
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 indiv
