On Aug 31, 2010, at 07:06, Nico Kadel-Garcia wrote: > On Tue, Aug 31, 2010 at 7:11 AM, Ryan Schmidt wrote: >> > >> It sounds like you are saying the following: >> >> * There is a file project.xml that developers should have in their working >> copy. >> * This file does not exist in the repository because it will be different >> for each developer. >> * There is probably even an svn:ignore definition for project.xml. > > What? Why do you assume that? Tech Geek said nothing of the kind, and > that's the part that would make it impossible. > >> * There might be a pre-commit hook blocking anyone from committing their >> project.xml. > > Again, what? Why do you assume that? > >> * You want to enforce that the developer cannot commit unless they have >> this project.xml in their working copy, though it will never be sent to the >> repository. > > It looks like Tech Geek has a trunk repository without the *.xml that > he (or she) wants developers to branch, build, and commit their > changes only when the build is successful and generates the *.xml > file. That's.... not unusual for building release tags or regression > tags. You do *not* want to tag something that doesn't even build.
Since the user didn't initially supply enough information for us to know what he really wanted, I made some educated guesses. Based on those guesses, I made some recommendations. It's all we can do in the absence of complete information. You did the same: you guessed that the user is using some branching / tagging technique; he didn't mention anything about that either. If our guesses aren't right, the user will correct us and hopefully we will eventually arrive at a solution, or at least an explanation of why a solution is not available.
