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

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

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.


 On Thu, 01 May 2003 20:49:43 +1000
Malcolm Tredinnick <ma...@co...> wrote:

> On Thu, May 01, 2003 at 02:35:20AM -0500, Joel Sinor wrote:
> > I forgot to mention that I did eventually find out what was
> > happening with Sourcemage.  Now, compiling by hand would have worked
> > in any case. At issue was a change they made for a bug.  I have not
> > tracked the bug # down and corrected it, but essentially they were
> > doing$ more /var/lib/sorcery/codex/stable/gnome/scrollkeeper/BUILD
> > (
> >   sedit "s/if xmlcatalog/if ! xmlcatalog/" configure
> >   default_build
> > ) > $C_FIFO 2>&1
> > $ 
> 
> Because they don't believe in "patch"?
> 
> > So essentially my theory is someone got the error for the DTD not
> > being there and changed this so they would not get the error.  I
> > will find out why eventually, but this of course has the result that
> > if you have the dependency installed you will fail.  Sourcemage
> > usually has things like this in their spell script config files to
> > fix broken ./configure and make files (or at least things that are
> > broken for their distro). This will not affect any normal
> > compilations, just compiles using their scripts.  I will let you
> > guys know when I find out more (have been fighting other battles).
> 
> Thanks for letting us know. That unfortunately reaffirms my earlier
> point though that, at least in my mind, Sourcemage are well on truly
> on the "distributions not be trusted in bug reports" list, which is
> going to really suck for their users. Completely breaking a package
> rather than fixing the core problem is disgraceful -- and you seem to
> indicate they do it often. There just are not that many 'broken' build
> processes out there that it's worth adopting a lax attitude to change.
> Those that are broken should be patched and bugs reported upstream to
> confirm that it really is a bug (this example was "fixed" by somebody
> who doesn't understand document build processes, for example).
> 
> Sorry, I'll stop ranting now. But really!
> 
> Not your fault though and thanks for the update. I'm going to go and
> have a lie down now.
> 
> Malcolm
> 
> -- 
> Tolkien is hobbit-forming.
> 
> 
> -------------------------------------------------------
> 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