enable dev mode on azure-pipelines-win to support source contains symlink

[trim21]

Checklist

• Added a news entry
• Regenerated schema JSON if schema altered (python conda_smithy/schema.py)

more details: conda-forge/mediainfo-feedstock#5

also cc @wolfv

[wolfv]

@jaimergp do you know if our content checks catch symlinks in packages on Windows? I think that should be disallowed for maximum compatibility.

[h-vetinari]

more details: conda-forge/mediainfo-feedstock#5

A reference is not a suitable argument - please don't make reviewers chase down rabbitholes; at least provide a short summary.

In general I would be against enabling symlinks simply because that makes it much more likely that we accidentally publish a package with symlinks, which would be broken on a large portion of windows clients. But given that the checkout in conda-forge/mediainfo-feedstock#5 fails because the sources contain a symlink, I can at least see the argument.

[do] content checks catch symlinks in packages on Windows? I think that should be disallowed for maximum compatibility.

This would of course be a solution. Assuming that they don't already check for symlinks, what I'd prefer to avoid is that this gets pushed off as unrelated here, and then never happens.

[trim21]

A reference is not a suitable argument - please don't make reviewers chase down rabbitholes; at least provide a short summary.

The title contains all the infomation I think, the link to that PR is just for the context.

[h-vetinari]

the title is the what, not the why

[trim21]

If we postpone this, is there an alternative solution I can put in place?

[trim21]

A workaround would be checkout git repo in build scripts.....

[isuruf]

Adding this might prevent checks about symlinks in conda packages right?

[trim21]

Adding this might prevent checks about symlinks in conda packages right?

Looks like we currently don't have symlinks checks for windows in conda-forge or rattler.build