sm-sorcery AT lists.ibiblio.org
Subject: Discussion of Sorcery related topics
List archive
- From: "Tyleanith" <tyleanith AT nc.rr.com>
- To: <sm-sorcery AT lists.ibiblio.org>
- Subject: [SM-Sorcery]Problem & Suggestion
- Date: Tue, 5 Nov 2002 16:42:17 -0500
Hello,
I've been happily installing spells and recompiling
for the past few days and testing stuff out. However today I noticed cast
--fix generated an error for the spell /usr/lib/libgcj.a saying this spell
doesn't exist (which I believe). Doing a gaze installed showed the
following spell: /usr.lib.libgcj.a:20021103:installed:1.1.4. Any idea what
went wrong and how should I go about fixing this? Just open up the file
and edit out the line?
And now for a few suggestions...
Sorcery->Option->Number of "make" jobs lets
you edit the number of jobs make uses which is nice. However it has a nice
big warning (which should be there). I was wondering, what if the spell
authors could add flags for a spell which specified if the build was 'multi job
safe'. It could have levels of, 'safe', 'unsafe', and 'untested'.
Safe would be run at the user's requested job #, unsafe would be forced into one
job, and untested would either be a 'sorcery->option->number of make'
option on how to run or a compile time question.
Also, does the "number of make jobs" setting cause
multiple spells to be cast concurrently, or just specify the -j flag to the make
call for each spell?
I installed the spell j2sdk without having X
installed. The build finished fine and it said successfull. A later
cast --fix showed it failed the integrity check. It mightbe useful to have
a flag specified where immeditaly after a spell is cast, an integrity check is
run on it. (Though my case may be special cause it involved
X).
Another thought was, having some sort of 'sorcery
dump-info [spell]' command. It would print out the version number of the
installed spell, versions of it's dependencies, what gcc/glibc verisons were
used to compile, what grimoire was used/installed, and any other info that might
be relivant. (Something might need to be done differently for 'attempted
installed version of spell' as well). It also might be useful to keep
around exactly what compile/sorcery options were used when building the package
(as far as I can tell this isn't being done). This also might help people
track down bugs/problems.
Scribe update. I'd really like to know when
the grimoire I download is different than the one I currently have
installed. There is the 'devel Updated!' message, but I don't trust this
as the message always shows up. It would be nice to see something
like
current devel grimoire is up to date. (or the
latest version or something).
updated devel [20021103] -> devel [20021104]
I'd also like to see something like scribe
update-test which would report back if there was a new grimoire but not actually
install it.
As well as the ability to back out a scribe update
somehow. Ex, you scribe, machine chokes, you unscribe, and are back to how
things used to be.
Thanks,
Tyleanith
I've searched the documentaion before posting and
didn't see any mention of the above features but I could have easily missed
something (specially on the scribe).
|
- [SM-Sorcery]Problem & Suggestion, Tyleanith, 11/05/2002
Archive powered by MHonArc 2.6.24.