Malcolm,
On 2006 May 25 , at 18.43, Malcolm J. Currie wrote:
>> By the way, the section which Malcolm added included a cross
>> reference to SSN/70, the URL for which was generated as <http://star-
>> www.rl.ac.uk/star/docs/ssn70.htx/ssn70.html>, but that gets a 404.
>
> I copied your later link to SSN/70; it doesn't prescribe a URL.
Indeed -- it's the sgmlkit which generates the URL. I'm just
remarking that this canonical URL seems to be broken. Is something
not being generated, or is the sgmlkit generating the wrong URL?
>> The only extra thing you need in order to build the documenation is
>> openjade, which is I think available as a Debian package, and
>> probably an RPM, too. With that findable, the sgmlkit component
>> builds and installs OK, and docs/ssn/078 ./bootstraps and builds OK.
>
> Not sure what to do in detail. Do we have to add checks for openjade
> availability, and install it on all the nightly build machines, or add
> it into thirdparty? I'm wary of treading here lest I break the build
> system again.
applications/sgmlkit/configure.ac has a STAR_SUPPRESS_BUILD_IF clause
which effectively skips the sgmlkit build unless it can find openjade
and osgmlnorm in the path. If they're missing, the sgmlkit build
succeeds trivially, and installs an empty manifest. In this case,
attempting to configure docs/ssn/078 will fail, as it won't be able
to find the sgml2docs script, which is part of sgmlkit. The same is
true for the one or two other documents which are written using XML.
If openjade is there, then sgmlkit will be fully built and installed,
and so docs/ssn/078 (etc) can be ./bootstrapped, then configured,
made and installed.
I can't now recall what precisely is the list of things which are
built in the nightly build. If that list includes SSN/78 (etc), then
all that's required is that openjade be somewhere on the path, and no
adjustment is required to the source tree.
Installing openjade into thirdparty wouldn't necessarily be a good
idea. That project has been a little more active recently, but when
I was setting this up, the openjade distribution wasn't terrifically
portable in fact, so that the .deb, .rpm and darwinports packagers
had to do a fair bit of work to make it build on those platforms,
which I reasoned we might as well lean on, rather than duplicating
that work in thirdparty.
See you,
Norman
--
------------------------------------------------------------------------
----
Norman Gray / http://nxg.me.uk
eurovotech.org / University of Leicester, UK
|