On Feb 27, 2005, at 11:03 AM, Basile STARYNKEVITCH wrote:
>
> I believe that this is a common scenario that one want to version a
> file produced by a command (be it a RDBMS dump, or an HTTP client like
> wget, or a GDBM dump...) and to ensure that the SubVersion system
> produces this file (by running this command) before commits.
Actually, no, in the general world of version control, it's considered
a Bad Practice to put "derived" files under version control. For
example, one doesn't put compiled (.o) files or binaries into the
repository. It's the *source* that gets managed, not the derived
objects.
The point of the start- and pre-commit hook scripts are to enforce
certain standards, not to generate more data to put in the repository.
For example, people often ask if it's possible to make the pre-commit
hook reformat code before putting it in the repository. The answer is,
"no, but it can be used to *reject* any commit that doesn't conform to
code formatting standards."
The sort of things you talk about above (making sure Subversion
"produces a file" before commits) is the domain of your build system,
not your version control system. The version control system should be
enforcing things, not building things.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Feb 27 18:32:37 2005