>Did you experience some surprising behavior?
No, but I thought I would ask before trying it :-)

Maybe the interesting case is the top level,perhaps a web-app, which would not be in the repo but might depend on a specific versions of EXpath packages. 
/Andy 

On 28 October 2015 at 12:48, Christian Grün <christian.gruen@gmail.com> wrote:
> Both the command REPO LIST and the GUI show the path within the repository.
> This information is not available from repo:list() for example as @path.

True. I think I'll add such a @path attribute. Thanks.

> Also I wonder about the support for multiple versions of EXPath packages?
> [1]

We are checking package versions and dependencies in our code, and we
have various test cases for that, but I have never excessively used
this by myself. Did you experience some surprising behavior?

Christian


> Given a repo with two versions of packageA, packageA-v1 and packageA-v2, and
> packageB that uses  packageA-v1 and packageC that uses packageA-v2, all
> defined in their respective expath-pkg.xml files.
>
> Would you expect this to work?
>
> /Andy
> [1] http://expath.org/spec/pkg#resolution
>
> On 27 October 2015 at 08:52, Christian Grün <christian.gruen@gmail.com>
> wrote:
>>
>> Hi Andy,
>>
>> I have spent some time in unifying our repository code, so this should
>> now be fixed [1]. Just give me an update if sth. else should be going
>> wrong now.
>>
>> Christian
>>
>> [1] http://files.basex.org/releases/latest
>>
>>
>> On Fri, Oct 23, 2015 at 11:02 AM, Andy Bunce <bunce.andy@gmail.com> wrote:
>> > Hi,
>> >
>> > The following installs in the repository, and can be used:
>> >
>> >
>> > "https://raw.githubusercontent.com/james-jw/xq-mustache/master/src/xq-mustache.xqm"
>> > !repo:install(.)
>> >
>> >
>> > But it does not appear the repo:list() or the UI repository list..
>> > I suspect the issue is the form of the namespace
>> >
>> > module namespace mustache = 'http://xq-mustache';
>> >
>> > Regards
>> > /Andy
>
>