Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

http://bugs.sourcemage.org/show_bug.cgi?id=13835





------- Additional Comments From acedit AT armory.com  2007-06-13 15:38 -------
This problem is certainly not a new one.

The suggested fix has come up before in other contexts. It probably will not
solve the modified config file problem entirely. From a cursory inspection it
seems like it might solve this instance of the problem. It also takes a step
down the path I had in mind for sorcery. Whether we're ready for that or not, 
I
dont know.

A solution thats been bouncing around on irc for a while is to not ever 
directly
touch the "live" config files. Instead they could be installed somewhere spell
specific, for example /usr/share/$SPELL/etc. This would effectively eliminate
the problem from view and normal operation.

This would be a conceptual shift in how our system works. Instead of 
installing
and managing config files, its left more up to the user (which could be good, 
or
bad). We already leave certain things to the user, such as starting and 
stopping
services. Other things we do control for the user, like init scripts.

>From a technical point of view staging makes this easy to implement on a
spell-by-spell basis. The alternative of course is to continue config file
management. The problem when viewed outside the context of an operating 
system,
in my mind, is not very different from the problem a revision control system 
solves.

I see two options for this problem: Either continue applying fixes as problems
are found, or avoid the situation by changing how files are treated.

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.