These general
guidelines describe EGL files that you will most
likely share in a repository or source-control system. The guidelines
also
cover some common problems you might encounter when sharing EGL projects.
The way that you share your
projects in a repository or source-control
system depends on the type of repository or source-control system.
In general,
share source files and build files but not derived files, files
that
are created from other files. This way, the files in the repository
are limited
to only those necessary for the application. (If you edit a file directly,
it is probably not derived.) For a discussion of derived files in
the context
of EGL, see Sharing projects.
Also, when you share projects in a repository, be aware of these
possible
problems:
- If derived files are checked into a repository, they
often lose their
derived flags. In this case, files that you normally wouldn't check
into a
repository may appear to need to be stored in a repository.
- Checking
files into a repository can break connections between files.
For example, if you check a UML model and a TPM file into a repository
and
then check them back out again, the workbench might not know that
the two
are associated. For
information on this problem, see
Linking
a UML model to an existing TPM file.
- When sharing
projects in a repository, the projects are subject to the
same potential errors as described in Sharing projects.