Jan Hendrik wrote:
> Separating the main config (input filename, location of images,
> where to put the output to) would be no issue, but part of the output
> production (print to file) has to be adjusted for each use
> (e.g. actual
> position of the image, standard copy each item might receive or
> not, depending on what it is).
Sounds like a use case for templating technology.
There is also this approach: store the adjustments as patches. Put
the original script and the patches under version control. Wrap the
checkout process to expand the patches into complete scripts in a
separate, not version-controlled, directory. Run and edit from this
separate directory. Before checkin, regenerate patches from the
expanded form, to capture any changes.
This may be the kind of clumsy hack you're looking for. It requires
some work, goes against the grain of the VCS, and there's at least one
race condition that I can think of. HTH, but don't tell anyone you
got the idea from me ;)
regards, Anders
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-05 12:27:35 CEST