Hello, we have our code repository managed by darcs, and I'm looking
for input on how to accomplish some version management the 'darcs way'.
The main file of interest is a which creates a database by way of SQL
commands. After that database is created, for production instances
of the database, we'd like to have an intermediate file which can
modify the database as it's running with more SQL commands.
As "incremental" file gets additional changes to apply to the
production database, the main file as its kept in the repository will
also get changed in the case that a production database needs to be
made from scratch.
So we basically have a moving target of files, and I was wondering if
darcs or darcs users have any methods for dealing with this. At the
very least, it'd be nice to get at the hash name for a particular
patch so that we could at the very least "name" the incremental file
after the hash name of the main file.
Any suggestions would be appreciated.
thanks,
-lev
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
