[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: exclude parts of a file from version control?

From: Jan Hendrik <list.jan.hendrik_at_gmail.com>
Date: Tue, 5 Aug 2008 18:30:48 +0200

Concerning Re: exclude parts of a file from ve
Anders J. Munch wrote on 5 Aug 2008, 12:27, at least in part:

> 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.

Yes, I have thought in that direction, too. But people here are not
very much in file operations. They expect that the application
(Word, Homesite) requests a name and handles the rest. Copying
a template of a script before using it will be something they easily
forget. And easily forget to copy back any modification which
should be preserved as general enhancement for future use, as
compared with modifications made just to fit the current operation.

> 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 ;)

Well, I may not! ;) This sounds quite error-prone and even clumsier
than what I had envisioned for splitting core script code and
configurable parts. Probably something in-between might work, not
perfectly, but still better than having no versioning of the script at
all: keeping a versioned master version outside of the general path
(probably really outside as an external) and a copy people can
work and play with, but not commit. From time to time I would
have to go in and see if there is something that should be kept and
added to the master. Or if there is anything they should not have
removed... Not ideal, but I know I asked for something almost
impossible ...

Thanks anyway, Anders!

Jan Hendrik

Freedom quote:

     Personal liberty is the paramount essential
     to human dignity and human happiness.
               -- Edward G. Bulwer-Lytton (1803-1873)

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 18:30:14 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.