Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

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





------- Additional Comments From acedit AT armory.com  2006-01-15 13:49 -------
The sorcery team already has plans for this in the works.

First of all, config files aren't backed up by cast in INSTALL, cast has no 
way
of knowing what config files a spell is going to touch until after it casts.
Sure it could make a good guess based on the install log, but it might not be 
right.

Second, there are two concepts of 'config' file, and theres also a concept of
'protected'. The config *filter* tells sorcery when a file is a config file 
and
to treat it specially, obviously if the spell is doing its own file 
installation
sorcery cant stop it, thats what install_config_files currently solves, its a
way of getting sorcery involved again. 'protected' is a different filter used 
by
dispel that keeps files from being removed, dispel also doesnt remove modified
config files by default. So now we wont get confused by terms as much.

I'm fully aware of how much install_config_files sucks, I wrote it, i dont 
like
it, but I needed something to get to here.

What we're doing in sorcery is using installwatch version 7 to transparently
translate file installation into a different directory. installwatch calls 
this
'transl', smgl has a related feature called 'INSTALL_ROOT'. INSTALL_ROOT
currently has to be implemented per-spell, with transl we get it for every 
spell
(assuming no one copies in files with a staticly linked libc, but we already
assume that since regular installwatch wouldn't work either). So, now we have
all the files in a seperate tree, we can do whatever we want and
install_config_files as spells use it is obsolete.

However, there are other problems to solve, most prominently, figuring out 
when
the file was last modified, and by whom. Not just users modify spell files,
other spells do too! So it becomes difficult to keep track of whether or not a
file was really modified or not. One possibility is to use distributed 
revision
control to keep track of file changes, which is effectively what any real
solution to the problem would be doing, whether they admit it or not. 
Although,
that adds another dependency to basesystem, which is lame. In anycase, we can 
be
more careful having full control over things.

I had planned on having something like this, <rant> although I hate calling it
the 'gentoo way of doing it', im sure they didnt invent it, and we're not just
re-inventing portage with sorcery, sorcery isn't portage. We can have our own
way of doing things, and I dont want people on the outside thinking we're just
copying gentoo, or people on the inside thinking we're just turning into 
gentoo. 
</rant>

Anyways whatever it is thats done will come after the installwatch work in 
1.14
is done.

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