Add larecs package

[samufi]

Add a recipe for the Larecs package

Logo could be a cone or twig of a larch tree (Larix decidua)

Checklist

• My recipe.yaml file specifies which version(s) of MAX is compatible with my project (see here for an example). If not, my package is compatible with both 24.5 and 24.6.
• License file is packaged (see here for an example).
• Set the build number to 0 (for new packages, or if the version changed).
• Bumped the build number (if the version is unchanged).

[carolinefrasca]

Hi @samufi, thanks for submitting this! Looks like it is failing on line 11. I think rev is supposed to be a commit hash (see screenshot from rattler build docs), but you should be able to use tag instead:

You could probably sub out that line for tag: "0.1.0"

 ╭─ Running build for recipe: larecs-0.1.0-h58ea7c0_0
 │
 │ ╭─ Fetching source code
 │ │ Fetching source from git repo: https://github.com/samufi/larecs.git
 │ │ Fetching repository from https://github.com/samufi/larecs.git at v0.1.0 into /Users/runner/work/modular-community/modular-community/output/src_cache/larecs.git
 │ │
 │ ╰─────────────────── (took 1 second)
 │
 ╰─────────────────── (took 1 second)
Error:   × Failed to run git command: failed to checkout FETCH_HEAD: error: pathspec
  │ 'v0.1.0' did not match any file(s) known to git

[carolinefrasca]

Line 11 needs to be updated (see comment on PR)

[samufi]

Hmm, the issue seems to be that I require a Mojo version that is available on nightly only. In the Forum, it was suggested that I can specify the max-nightly requirement somewhere in the recipe, but I did not find anything else besides the place where the max version is specified. I'd welcome assistance.

[carolinefrasca]

Hi @samufi, unfortunately adding this nightly breaks the Mosaic package – let me reach out to the owner and ask them to update their package, and then once that's done, I can add that nightly to the channel.

[samufi]

@carolinefrasca I have updated Larecs to the second release, which uses the stable Mojo branch. Could you restart the checks so that we can see if the package can be merged?