Skip to Content.
Sympa Menu

sm-grimoire - Re: [SM-Grimoire] Scrollkeeper/Docbook issue

sm-grimoire AT lists.ibiblio.org

Subject: Discussion of Spells and Grimoire items

List archive

Chronological Thread  
  • From: Joel Sinor <jsinor AT comcast.net>
  • To: sm-grimoire AT lists.ibiblio.org
  • Subject: Re: [SM-Grimoire] Scrollkeeper/Docbook issue
  • Date: Tue, 06 May 2003 14:12:21 -0500

On Sun, 04 May 2003 14:23:35 -0700
Amy Lear <amy AT heliophobic.net> wrote:

> This was originally sent to sm-users, but then I realized (after
> waking up the rest of the way and staring at the screen crosseyed)
> that isn't where I wanted it to go.
>
> It might be a wee bit more useful over here, so here it is.
>
>
> Trying Sourcemage again for the first time in a long while (last time
> I tried this distro, it was just before the rename)..
>
> I'm experiencing the wonderful joyous scrollkeeper/docbook issues,
> where scrollkeeper is complaining that I need docbook-dtd 4.1.2, even
> though I have 4.1.2 installed. I did a bunch of research using the
> forums and this mailing list, found some relevant Bugzilla entries..
>
> Looks like bug #180 ( http://bugs.sourcemage.org/show_bug.cgi?id=180 )
> explains the problem pretty clearly: the hack that was added to the
> scrollkeeper build fixes building with docbook-dtd 4.2.0, but breaks
> 4.1.2. Yet the stable grimoire has 4.1.2, not 4.2.0.
>
> So, I copied the docbook-dtd spell from devel to stable. This appears
> to correct the issue.
> _______________________________________________
> SM-Grimoire mailing list
> SM-Grimoire AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-grimoire


The scrollkeeper people have spoken. I was trying to find out a better
way of fixing the sourcemage scrollkeeper bugs, since I did not think it
was a good idea to make sure that the user does not have the prereqs
installed in order to install a program. The scrollkeeper developers
appear to have decided they were wrong in requiring an absolute version
in the first place. So when this is fixed, we can get rid of the sedit
problem altogether.

> To try and clear this matter up: the problem is because scrollkeeper
> does not currently detect the absolutely latest verison of Docbook.
> That is a bug in Scrollkeeper. There is even now a bug at sourceforge
> for it(filed a few days ago). It will be fixed by making configuration
> scripts for scrollkeeper try to detect a few different Docbook
> versions, falling back from most recent to oldest. Once that change is
> made, it will be easy to handle future Docbook upgrades.
>
> Hopefully this should make everybody happy and prevent a reoccurence
> of this debacle in the future.
>
> Malcolm




Archive powered by MHonArc 2.6.24.

Top of Page