Skip to Content.
Sympa Menu

sm-grimoire - Re: [SM-Grimoire] Starting from scratch (again)

sm-grimoire AT lists.ibiblio.org

Subject: Discussion of Spells and Grimoire items

List archive

Chronological Thread  
  • From: "Sergey A. Lipnevich" <sergey AT optimaltec.com>
  • To: Duane Malcolm <d.malcolm AT auckland.ac.nz>
  • Cc: Andrew <afrayedknot AT thefrayedknot.armory.com>, sm-grimoire AT lists.ibiblio.org
  • Subject: Re: [SM-Grimoire] Starting from scratch (again)
  • Date: Tue, 10 Jun 2003 19:34:50 -0400

Duane Malcolm wrote:

1. CVS update of the grimoire. Amazing for someone with a 56k modem.

That's smart, and grimoire's user actions really resemble that of a programmer developing source code. What happens if there's a conflict though? CVS will effectively destroy the file's value with ">>>>>>>". I think rsync is much more suitable here.

3. xdelta updates, again a great feature for someone with a 56k modem

Why? If there's CVS updates...

4. During an email conversation with Kyle, he mentioned he was wanting to get the grimoire down to 1024 spells or less. And after thinking about it. I think it's a great idea. I read an article about how a flaw with linux is there are to many people rewriting software instead on supporting, developing or adding missing features to current software. That's not to say there shouldn't be a few of the same type of application, ie. mozilla, galeon, etc... But anyway, let's say there was a core grimoire and an extras grimoire, the core grimoire would include the best of your basic software and the extra will include others. Over time spells in the extra grimoire can be moved into the core grimoire if it's supported by number of Sourcemage users. Because the core grimoire is small, Sourcemage will find it easier to support a core grimoire and be confident it works together.

I don't see the point. How's supporting 2000 spells is different from 1000? If somebody wants a new spell, s/he creates it, and then somebody who needs it will fix it if it's broken. Spells that belong to the core are maintained all the time because they're needed by many. That's effectively the core of it.

Other features:
1. Sorcerer has also moved the DEPENDS file into the DETAILS file, so similar to SOURCE[0], SOURCE[1], etc.. it lists the dependencies by having DEPENDS[0]=..., DEPENDS[1]=..., OPTIONAL[0]=...., OPTIONAL[1]=....

We have if statements in DEPENDS sometimes.

2. Can cast most of the recent versions of spells, eg, cast mozilla,1.3a or cast mozilla,1.4, there are a default set of BUILD, CONFIGURE files and if the BUILD is different from default there is a BUILD,1.4 file.

So that eventually the grimoire will grow to unmanageable size having all Mozillas from 0.9.7 to 10.11.12?

3. It also has a flag for the size of the source which can give an estimate of the download size.

We can jam that into MD5 preparation routines when they're sufficiently automated.

4. Compile viewer gave a % completion for the compilation of a spell also had simutaneous casting. Craig will tell you more about this. This is what crashed during my rebuild process and where I gave up.

I have 100% CPU utilization during compilation all the times and on different systems. How would running two GCCs at once improve timing?

Duane.

Thanks a lot for this write-up!

Sergey.





Archive powered by MHonArc 2.6.24.

Top of Page