On 15 October 2013 13:51, Earnie Boyd wrote:
On Tue, Oct 15, 2013 at 5:14 AM, Keith Marshall wrote:
> [...snip...]
> Furthermore, mingw32-gcc4.xml is still missing the
> necessary requirements declarations, on gcc-core-bin, to pull in w32api,
> mingwrt, and binutils; (why is the last of these not simply declared as
> a requirement of the component, rather than an explicit requirement of
> each individual release?  The requirement is identical for all).

Because they are not identical across all versions.

The last of them (binutils) *is*.  It's an entirely generic reference to
"latest available version".  That could easily be moved, to apply to all
releases, without having to declare it every time.

Granted, the mingwrt and w32api requirements differ, and they do need to
be individually specified for each release; I never suggested otherwise.

I could see a benefit for something like

<release id="gcc-4.8.1">
  <requires eq="mingwrt-4*-mingw32-dev.tar.lzma"/>
  <requires eq="w32api-4*-mingw32-dev.tar.lzma"/>
  <release tarname="gcc-core-4.8.1-4-mingw32-bin.tar.lzma">
    <requires eq="gcc-core-4.8.1-4-mingw32-dev.tar.lzma"/>

I don't see what you're trying to achieve here; the XML schema will not
permit you to embed a release element within another, and even if it
did, mingw-get would not know what to do with it.