Re: [Mingw-users] mingw-get : dependencies not downloaded

[Keith M. <kei...@us...>]

On 30/07/11 16:29, Vincent Torri wrote:
>> ...  The name attributes don't match, so the dependency isn't
>> resolved.
> 
> ok. Indeed, it works now, thank you.

Good.

>> Do note that this isn't a downloading issue.  The "*** ERROR ***"
>> messages you see are generated during construction of the dependency
>> graph, before any downloading commences; mingw-get simply knows that
>> there is a dependency, but it can't work out what package is needed to
>> resolve it, because you don't specify a "gnutls" package which provides
>> the required dll component.
> 
> ok, i thought that it was the name of the file (because of the 'tar' 
> extension).

Nope.  The match (lt, le, eq, ge, or gt) attribute is decomposed, using
the same back-end pkginfo() function as pkginfo.exe, to extract the
package name, subsystem name, component class and various version id
fields; mingw-get then searches the XML tree, within package-collection
elements with a matching subsystem attribute, for a component element
matching the specified class attribute, and embedded within a package
element with a matching name attribute or alias.  Only when it finds
such an element, does it then search for the best-fit version of the
associated package, among its contained release elements, and it's only
here that it finds actual file names, (where the "tar" extension does
become significant; as explained in the following paragraph, it has no
special significance within the "requires" specification itself).

The specification of "tar", (as package format), in the "requires"
specification is entirely arbitrary in this particular context; some
format qualifier *must* be present, else pkginfo() -- a flex generated
lexical analyser function -- becomes hopelessly confused.  However, the
actual value here is irrelevant -- it could just as well be "foo",
"bar", or "quux"; we choose "tar" simply because that's the format we
use for all our packages, so it seems a logical choice.  Apologies if
that has caused any confusion.

-- 
Regards,
Keith.