sm-sorcery-bugs AT lists.ibiblio.org
Subject: Bugs for Sorcery are reported here
List archive
[SM-Sorcery-Bugs] [Bug 6725] sorcery support for testing if files are installed and track them
- 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 10:49:04 -0400
http://bugs.sourcemage.org/show_bug.cgi?id=6725
------- Additional Comments From hgreig AT bigpond.net.au 2004-04-15 10:49
-------
Jason, I appreciate that you think I would be good for that job, but no
thanks.
Andrew,
1) Although your suggestion is a good one, the projects options are limited
by
its having less than ten active developers. It should only be used for
CROSS_INSTALL. If you have ever looked into a rpm spec file you will know the
hacking that goes into installing to a tmp location and then copying across.
The less overheads for spellwriters and grimoire team the better I think.
Basesystem and some few extra spells currently works for my ISO production,
and after that the user is on their own. In the future, this could change.
2) should likely be permanently implemented along with a new variable in
DETAILS that tells sorcery which additional files should be covered by
sorcery's reap function (is that what is called ?, the one that stops SA
modified files from being removed ?). This would cover "make install"
commands
that try to install config files regardless of whether they already exist or
not.
3) & 4) the spells I mention specifically do
if ! [ -f /etc/$file ]
then cp -f ./$file /etc/
fi
an etc_cp() function would replace the whole if ...fi loop, it would check,
and if it already existed, touch it to track it, then install $file to
$file.default, else if it didn't exist, it would install it to $file.
the reap function would stop it from being dispelled/removed if the user had
customised it so I think this approach would work 100% of the time.
For config files not in /etc the extra variable in DETAILS would stop them
from getting reaped too, and it would then work in that scenario too.
I know my explanation is simple, but I think you follow my train of thought
well. let me know if you need further clarification.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-
[SM-Sorcery-Bugs] [Bug 6725] sorcery support for testing if files are installed and track them,
bugzilla-daemon, 04/15/2004
- <Possible follow-up(s)>
- [SM-Sorcery-Bugs] [Bug 6725] sorcery support for testing if files are installed and track them, bugzilla-daemon, 04/15/2004
- [SM-Sorcery-Bugs] [Bug 6725] sorcery support for testing if files are installed and track them, bugzilla-daemon, 04/15/2004
- [SM-Sorcery-Bugs] [Bug 6725] sorcery support for testing if files are installed and track them, bugzilla-daemon, 04/15/2004
- [SM-Sorcery-Bugs] [Bug 6725] sorcery support for testing if files are installed and track them, bugzilla-daemon, 04/18/2004
- [SM-Sorcery-Bugs] [Bug 6725] sorcery support for testing if files are installed and track them, bugzilla-daemon, 04/18/2004
Archive powered by MHonArc 2.6.24.