how to override &release.latest; ?

For the pc532 ports page, I'd like to override
&release.latest; and set it 
to 1.5.3, as that's when the port was last released in
binary. How does 
one do that?

Here's what doesn't work:

 	<!DOCTYPE webpage
 	  PUBLIC "-//NetBSD//DTD Website-based NetBSD
Extension//EN"
 	         "http://www.NetBSD.org/XML/htdocs/lang/sh
are/xml/website-netbsd.dtd" [
===>	<!ENTITY release.latest "1.5.3">
 	]>

The <portspage> tag uses release.latest (and some
others.

Any ideas?


  - Hubert

On Sun, 8 Apr 2007, Hiroki Sato wrote:
> I think something like the attached patch is needed. 
You can think the 
> scope and linkage of an entity reference (&foo;) is
"static" storage 
> class in C language.  The &foo; defined in an XML
file, it can be used 
> in the same XML file, but not in the XSL stylesheet. 
So, redefining 
> &release.latest; in the XML file does not affect
the templates for 
> <portinfo> in the XSL stylesheet.

Sounds good... will this default to set
currel=&release.latest; if it's 
not given explicitly? (We don't want to hardcode the release
number on all 
ports pages)

Sorry my xslt-fu is not strong enough to verify/implement
this. :(

Thanks!


  - Hubert

Hubert Feyrer <hubertfeyrer.de> wrote
  in <Pine.LNX.4.64.0704081524510.9004m2s05.vlinux.de>:

hu> On Sun, 8 Apr 2007, Hiroki Sato wrote:
hu> > I think something like the attached patch is
needed.  You can think the
hu> > scope and linkage of an entity reference
(&foo;) is "static" storage
hu> > class in C language.  The &foo; defined in
an XML file, it can be used
hu> > in the same XML file, but not in the XSL
stylesheet.  So, redefining
hu> > &release.latest; in the XML file does not
affect the templates for
hu> > <portinfo> in the XSL stylesheet.
hu>
hu> Sounds good... will this default to set
currel=&release.latest; if it's
hu> not given explicitly? (We don't want to hardcode the
release number on all
hu> ports pages)

 Ah, the patch in the previous mail does not set the default
value,
 but it is possible and sounds reasonable.  I committed a
revised
 patch to do so to portpage.xsl just now.

--
| Hiroki SATO

On Sun, 8 Apr 2007, Hiroki Sato wrote:
> Ah, the patch in the previous mail does not set the
default value,
> but it is possible and sounds reasonable.  I committed
a revised
> patch to do so to portpage.xsl just now.

Thanks, that works.

But it also raises more problems:
  * The release is in /pub/NetBSD-archive (not
/pub/NetBSD),
  * the release announcement is in
    htdocs/Releases/formal-1.5/NetBSD-1.5.3.html (not
    htdocs/Releases/formal-1/NetBSD-1.5.3.html)
  * Changes are in htdocs/Changes/changes-1.5.html (not
    Changes/changes-1.0.html)

Shall we add more keywords to the <portinfo> tag to
override the defaults, 
or is there a better way?


  - Hubert