Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 6725] sorcery support for testing if files are installed and track them

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT metalab.unc.edu
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 6725] sorcery support for testing if files are installed and track them
  • Date: Thu, 15 Apr 2004 02:16:52 -0400

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





------- Additional Comments From acedit AT armory.com 2004-04-15 02:16 -------
Just so I understand, the problem as I see it is:
files get installed to /etc, but on an upgrade if they are different
some spells are 'smart' enough not to overwrite the old files, but in
doing so fail to continue tracking the new files.

so just letting the ideas flow for a second. We could have a command
say 'track_file' that one could call on certain files so sorcery would
add it to its list of files it thinks its tracking. Then all those
special /etc files could be tracked under all circumstances.
This etc_cp thing could call that for either case (copies the file,
or makes a foo.default file)

In my perfect world sorcery would take care of keeping config files from
crushing each other automatically. This could be done several ways.

1) change the INSTALL_ROOT to always be somewhere off of / then copy the
files manually. An unnamed distro does things this way. With the
new building infrastructure going in creating a new build pipeline
that runs in this way would be fairly easy. The hard work is
making spells use INSTALL_ROOT, but since the building infrastructure
allows spells to use whichever build api they want, we can just convert
the spells over as needed.

2) use the awesome power of installwatch's backup feature to save the
files that get trampled and then fix the problem after the fact.
I dont know how this undocumented feature of installwatch works, so
who knows if it will work.

3) make all spell writers be more careful about config files and perhaps
define an api for doing so. I think this is what hamish is describing.

4) seperate out the config files from the tracked list and on
dispel/prepare_install copy them to a safe-haven somewhere, let the
spell install things where it wants. Then manually copy the files
back over that have changed.

Theres of course this underlying assumption that all config files
live in /etc and nowhere else. Which should be true, but isn't.
So Im sensing that somehow spells should be able to define additional
config files (say we add a new file or something).

Any of the other ideas sound attractive?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page