Quote: |
> But the disadvantage of that is that > then you end up having to maintain two separate rmaps which is the kind > of thing we're trying to avoid with the Buckminster approach in the > first place. > You are right. Don't know the best practices here, if it is possible to do something clever - can someone else fill in? |
Quote: |
As you can see, the idea is to use different policies at different times while still using the same description and mechanisms. I.e. developers typically want a different setup (trust dirty workspace), whereas on a server for a more official build a dirty workspace is forbidden. With this separation it should also be possible to drive the Hudson "watch the SCM" feature from a single description. |