Triton 2.0

[hmaarrfk]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[hmaarrfk]

@h-vetinari i noticed that you are doing some work on llvm-lit. Would you like me to wait for your llvm work to go through?

I wasn't able to get this to compile with newer llvm. Would you like me to show you the logs?

[h-vetinari]

@h-vetinari i noticed that you are doing some work on llvm-lit.

Well, I did tag you in conda-forge/llvmdev-feedstock#210 ;-)

Would you like me to wait for your llvm work to go through?

Not necessary IMO it's just for making things easier with lit. I'm waiting for a comment from Isuru then I can merge, but getting it into the maintenance branches too will take longer than is worth waiting.

I wasn't able to get this to compile with newer llvm. Would you like me to show you the logs?

Not sure what the upstream compatibility is. But if it's an issue of the conda-forge packaging, then we can have a look of course.

[hmaarrfk]

Ok let's merge for now and troubleshoot in subscribe PRS