On 18/03/13 13:53, Earnie Boyd wrote:
> Will something like the following work?
> <release tarname="mingwrt-3.*-mingw32-%-dev.tar.%" />
> <release tarname="mingwrt-4.*-mingw32-%-lic.tar.%" />
No. For these reasons:
1) A release tag is significant *only* when it appears as a child of a
package tag, or as a grandchild of a package, with a component tag as
its immediate parent. While you may specify children within a licence
tag, (remember, there is no formal DTD or schema to prohibit it), none
will be accorded any meaning.
2) You cannot use wildcards within the tarname attribute of a release
tag, (as a child of a package or a component), since this is where a
*specific* version is *defined*.
3) The licence tag itself requires a tarname attribute. No *matching*
is performed on this; only field-for-field substitution for '%' tokens,
from the referrer tarname.
What you *can* do is specify a generalised substitution licence spec for
the package, then override it for individual releases, by adding a more
explicit licence spec as a child of the release tag itself:
<!-- package global licence specification: -->
<!-- applies to all releases which don't stipulate otherwise -->
<licence tarname="mingwrt-%-mingw32-%-dev.tar.% />
<!-- override global licence reference -->
<licence tarname="wsl-4.0-1-mingw32-rc-1-lic.tar.lzma />
<!-- other releases use the package global licence -->
<release tarname="mingwrt-3.20-2-mingw32-dev.tar.lzma />