Unable to specify file containing - in remap of inputs

[mwhapples]

I am trying to package an application. I start with a directory containing all the files needed. There are some platform specific subdirectories (eg. windows-x86_64, linux-x86_64, etc) which I only want distributed for the specific platform. So my thought is to add the directory to inputs and use remap to exclude the platform specific ones and then have these platform specific directories added as inputs for those machines.
My problem though is specifying the remap patterns to exclude these directories. Taking the windows-x86_64 directory as an example. If I give the pattern "-windows-x86_64/" in the remap then windows-x86_64 is still being included. The closest I can get is giving the pattern "-windows?x86_64/" which successfully excludes the directory.
Whilst using a wildcard to match the - works, it feels wrong as I cannot specifically match a path, the wildcard may wrongly pick up other matches.
So how should I match a - in a remap pattern?

[mikehearn]

That sounds like a bug. We will investigate!

[mikehearn]

Ah yes, I see that part of your post is accidentally bolded :)

Could you show me the entire snippet of config for the inputs you're using? Maybe it's an ordering issue.

[mwhapples]

Now I am confused, I cannot reproduce the issue as I previously found it. I had been experimenting with other patterns and now when I change it back to what I thought I had it all seems to work fine. So what is different now I don't know but where I have got to seems to work as expected. This is what is working for me:

    inputs += {
        from = dist
        remap = [
            "**"
            "-lib/linux-x86_64/**"
            "-lib/mac-x86_64/**"
            "-lib/windows-x86_64/**"
        ]
    }

Thanks for your time and sorry it turns out I cannot actually find what previously happened to give something unexpected.

[mwhapples]

I think the docs may be fine. I initially made the mistake in not noticing the need for globs, but I quickly spotted that and had accounted for it in the conf file before posting here.

[mwhapples]

Let me know if you want me to try reproducing it with a minimal example and trying to get some steps to reproduce. Otherwise I am happy with how it is working now and could easily write it off as some typo or other mistake and not spotting the error due to seeing the code I expected to see rather than the mistake.

[mikehearn]

Hmm very odd. No problem though. If you figure out what was different, let us know. Note that the logs directory contains logs for the past 20 or so runs, I think.