a method slightly out of the CVS system might be to have two module names to
checkout, one for binary production and another for coding and testing.
code_module checks out everything but the binary directory and the Makefile tests
for the existence of the bin directory, if not found it is made (a directory as a
target) thus the bin dir is not a cvs controlled item.
product_module contains code_module and the bin dir when checked out so when the
binaries are made they can be version controlled.
David Martin wrote:
>
> Matt --
>
> Thanks for your comments.
>
> Matthew Berney wrote:
>
> > What is the requirement that you are trying to satisfy? Why do you need to
> > exclude updates?
>
> The subdirectories, such as "c" in my example, contain binaries corresponding to
> the source code in their parent directories (such as "b"). We would like to be
> able to use CVS to make snapshots of the binaries at certain points in time, but
> we don't want the binaries to be updated or committed every time someone runs
> update or commit in the source code directory.
>
> As I mentioned, I realize there are already some ways to prevent the updates
> from applying to the binaries, but I'm looking for something that doesn't place
> any new constraints on the developers. That is, no matter what form of update
> or commit command a developer wants to use, I'd like to ensure that it doesn't
> apply to the subdirectories containing the binaries.
>
> I realize it would make sense just to move the binaries out of the source code
> hierarchy, and make our binary snapshots from the new location. But this creates
> some other complications, so -- as always -- I'm just looking for the solution
> with the greatest simplicity and the least overhead.
>
> -- David
>
<SNIP>
