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

[Vincent T. <vt...@un...>]

Hey

On Sat, 30 Jul 2011, Keith Marshall wrote:

> On 30/07/11 12:08, Vincent Torri wrote:
>> mingw-get.exe: *** ERROR *** curl-7.21.7-mingw32-dll.tar.lzma: requires...
>> mingw-get.exe: *** ERROR *** gnutls-2.12.7-mingw32-*-dll.tar: unresolved dependency (type 'eq')
>> mingw-get.exe: *** ERROR *** gnutls-2.12.7-mingw32-*-dll.tar: cannot identify any providing package
>> mingw-get.exe: *** ERROR *** please report this to the package maintainer
>>
>> ...snip...
>>
>> So it does not find the gnutls archive, while
>>
>> mingw-get install libgnutls
>>
>> works. I double check the directories, but i think that i have looked at
>> that repository too much, so another look might be helpful.
>>
>> Any idea what is wrong ?
>
> Without looking at the actual XML content, the above suggests that your
> "requires" statement within the "curl-dll" package is:
>
>  <requires eq="gnutls-2.12.7-mingw32-*-dll.tar"/>
>
> which mingw-get reads as an instruction to look for the gnutls-dll in a
> package specified something like:
>
>  <package-collection subsystem="mingw32">
>    ...
>    <package name="mingw32-gnutils" alias="gnutls">
>      <component class="dll">
>        ...
>      </component>
>    </package>
>  </package-collection>
>
> whereas, in reality you have:
>
>    ...
>    <package name="mingw32-libgnutls" alias="libgnutls">
>    ...
>
> or similar.  The name attributes don't match, so the dependency isn't
> resolved.

ok. Indeed, it works now, thank you.

> 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).

> I guess you need to write the dependency specification as:
>
>  <requires eq="libgnutls-2.12.7-mingw32-*-dll.tar"/>
>
> You might find it helpful to run this specification through pkginfo:
>
>  $ ./pkginfo.exe libgnutls-2.12.7-mingw32-*-dll.tar
>  Package Name:      libgnutls
>  Package Version:   2.12.7
>  Package Build:     <unspecified>
>  Subsystem Name:    mingw32
>  Subsystem Version: *
>  Subsystem Build:   <unspecified>
>  Release Status:    <unspecified>
>  Release Reference: <unspecified>
>  Component Type:    dll
>  Component Version: <unspecified>
>  Archive Format:    tar
>  Compression Type   <unspecified>
>
> The "Package Name:" element here *must* match either the "name"
> attribute, or any one the the space separated alternatives within an
> "alias" attribute in the providing "package" specification element, and
> the "Component Type:" element must match the "class" attribute of a
> "component" element contained within that "package" element.

ok

> BTW,
>
>> $ mingw-get install libcurl
>> Update catalogue: efl-package-list.xml
>> Update catalogue: mingw32-jpeg.xml
>> Update catalogue: mingw32-freetype.xml
>>
>> ...
>>
>> Update catalogue: mingw32-curl.xml
>> Update catalogue: mingw32-lua.xml
>
> You might consider adding the "efl-" prefix to *all* your catalogue
> names, (not just to the primary package list), to avoid any possible
> contention with similarly named catalogues from other repositories.  One
> day I'll get around to hashing catalogue names, per repository, to avoid
> such contentions, but for now, declaring your own "namespace" is the
> best practice to adopt; (unadorned "mingw32" or "msys" might be
> construed as trampling on ours).

I'll do it.

thank you

Vincent Torri