Update to version 0.8.0 and include support for Windows.

[vtraag]

Checklist

• Used a fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• 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.

This PR updates igraph to version 0.8.0. Unlike PR #14, this also includes support for Windows. The support for Windows is submitted separately in this PR, so that if any issues present themselves, it doesn't conflict with the update to version 0.8.0 for other platforms, and PR #14 can still be merged.

There are hence two options: (1) all goes well, and we can merge this PR (in which case we should set the build number to 0); (2) problems galore, in which case PR #14 could simply be merged, and I continue working on this PR.

[conda-forge-linter]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [8, 9, 10, 27, 28, 29, 30, 33, 34, 35, 36, 37, 38, 40, 41, 42, 43, 44, 45]

[vtraag]

@conda-forge-admin, please rerender

[conda-forge-linter]

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.

[conda-forge-linter]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [28, 51, 56]

[conda-forge-linter]

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.

[vtraag]

It took some time, but I think option (1) should now be followed, and this PR should be favoured over PR #14. I have reset build number to 0, and this could be merged.

[vtraag]

@conda-forge-admin, please rerender

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-webservice.

I tried to re-render for you but ran into some issues, please ping conda-forge/core for further assistance. You can also try re-rendering locally.

[vtraag]

Ping @sodre could you please take a look at this PR?

I'd be happy to be added as a maintainer of this feedstock. I am currently commited to the development of the igraph project itself. Maintaining the conda feedstock would then only make sense from that perspective, and I am already a maintainer of python-igraph feedstock.

[vtraag]

Note that this PR also fixes the issue addressed in PR #7, which can then also be closed.

[sodre]

@conda-forge-admin, please rerender

[sodre]

@conda-forge-admin, please rerender

[sodre]

LGTM, I am just waiting for the windows build to pass again before merging.

[conda-forge-linter]

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.

I do have some suggestions for making it better though...

For recipe:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.