[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bitkeeper-users
Subject:    Re: [Bitkeeper-users] BK best practices (project organization)
From:       Jules Colding <jules () tdcadsl ! dk>
Date:       2004-05-06 6:37:14
Message-ID: 1083825434.12940.6.camel () linux-1
[Download RAW message or body]

On Thu, 2004-05-06 at 00:42, Matthew Knepley wrote:
> Jules Colding <jules@tdcadsl.dk> writes:
> > Well, yes.. that would work. But having the relation at the version
> > control level would offload that dependency tracking to the version
> > control system (bk in this case) which knows all about the changes in
> > the parent repo. 
> > 
> > It just seems that it would be a lot easier to have that kind of
> > intelligence in bk, than having to reinvent the wheel for each of these
> > build systems.
>     This just does not seem workable at all. You have no guarantee that
> changes in an IDL file will result in changes to generated files. Furthermore,
> you would have no idea at all which files had changed, even if you assume
> a change happened.
>     If you are using BK to tell you what files changed in the dependent repo,
> then just use that check. The upstream check of the IDL file is meaningless.

Hmm, I am not sure that I understand what you mean by that... Any change
in an IDL file (except for whitespace and comments) will result in a
change in the generated files. Please correct me if I am wrong on this. 

But, I do agree that it would be a hard problem to figure out what
would/should happen if the parent repo is cloned/tagged or in some other
way split into two distinct development paths.

The inheritance coupling would be very tight indeed, but maybe you are
right that a build system is the better/simpler way to solve the
problem.

Best regards,
  jules

_______________________________________________
Bitkeeper-users mailing list
Bitkeeper-users@bitmover.com
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.
[prev in list] [next in list] [prev in thread] [next in thread]