> -----Original Message-----
> From: Dimitri Papadopoulos-Orfanos [mailto:firstname.lastname@example.org]
> Sent: Monday, November 07, 2005 2:04 PM
> To: email@example.com
> Subject: Re: Build question
> > For example, you could have a special text box control that is used
> > several projects. Would something be wrong when it is built with
> > (client-) applications? Is something wrong designed when I have to
> > from different repositories?
> > I'm a newbie not an expert, so tell me please if I do something
> > stupid...
> I see two solutions:
> 1) Either the special text box control is very closely interconnected
> all other projects. In that case all projects should live in the same
> repository and have a global revision number that describes the state
> the whole set of projects.
I think this cannot be the proper way. If there are further items that
shared differently to the special text box then this structure wouldn't
work (Control A is used by project 1 and 2 and control B is used by
project 1 and 3).
> 2) Or the special text box control is loosely related to the other
> projects. In that case it lives a life of its own and it should be
> available through proven methods: software releases, versioning, etc.
> Typically you would never synchronize with the HEAD revision of the
> special text box control, instead you would synchronize with a
This seems to me the only advisable approach.
> Anyway, what are you afraid of? What could happen to the special text
> box control and to your other projects during the build process? What
> the probablity that happens in the short term? And if that happens,
> can't it be fixed without too much hassle?
I just wanted to make the use of subversion save and reliable somehow. I
assumend that someone could commit something when the build process is
running. This shouldn't cause an problem.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Nov 7 14:30:04 2005