Re: [Scrollkeeper-devel] problem with configure script on scrollkeeper 0.3.12 *SOLVED!*

[Joel S. <js...@co...>]

That is good news.  I was wondering why your configure script was being
absolutist about versions, but then there are many reasons sometimes.  I
will pass this on to the sourcemage team since we are currently
considering how to fix the bug on our side ;).

 On Tue, 06 May 2003 11:53:45 +1000
Malcolm Tredinnick <ma...@co...> wrote:

> On Mon, May 05, 2003 at 04:03:06PM -0500, Joel Sinor wrote:
> > I have since got further information from the Sourcemage team:
> > > This was done because in the devel grimoire docbook-dtd is at
> > > version 4.2.0 and since scrollkeeper isn't updating to use it we
> > > had to do that script to stop the build process from failing.  If
> > > the test and stable grimoires are not updated to the docbook-dtd
> > > 4.2.0 then that needs to be removed for them.
> > > 
> > 
> > I of course replied the following:
> > Aha! To be fair, Eric was nice enough to send me a list of all the
> > bugs, and I just haven't gotten round to reading up on them and
> > submitting my own.  Actually my plan was once I figured out why it
> > was done to figure out a better fix.  Requiring that the docbook
> > *NOT* be installed is IMHO a bad way to fix this problem.  
> > As for test and stable, well, they will of course catch up with
> > where devel is now eventually, but this begs the question of what
> > happens if I install the new version of the dtd?  (Before I got this
> > error I knew pretty much zero about docbook, and even aftre I pretty
> > much only know what happens when you use the commands in
> > scrollkeeper's configure script ;) )  I mean will tests for the old
> > version still say it is there(will it be there?) or when it is
> > upgraded is it replaced completely with no trace it was ever there?
> > 
> > ---
> > Anyhow, I am wondering if you guys can answer my docbook questions. 
> > I am working on a better way to fix the sourcemage problem.  I am
> > leaning currently toward making the "sedit" on the version number of
> > the docbook dtd rather than doing what they were doing before, which
> > is making it so that the dtd cannot be installed if you want to
> > install scrollkeeper.
> 
> I have lost track a bit of what is quoting from other sources and
> what is directed to this list in the above, but it doesn't really
> matter.
> 
> 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
> 
> -- 
> Experience is something you don't get until just after you need it.
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Scrollkeeper-devel mailing list
> Scr...@li...
> https://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel