Skip to content

Renaming compiler package to nim conflicts with setting Nim version requirements? #21546

Open
@elcritch

Description

@elcritch

Description

Nimble uses requires "nim >= 1.6.0" as a common idiom. However, recently it looks like the Nim compiler package was renamed to nim.

However, this conflicts with the previous ability to require minimum Nim versions. If the goal is to allow using the current system Nim instead of installing a new compiler package that's great but it doesn't appear to work that way at this time.

Nim Version

Nim 1.6.12

Current Output

Warning: Using the environment variable: NIMBLE_DIR='/Users/jaremycreechley/.nimble'
Downloading https://github.com/elcritch/ants using git
   Warning: Package 'ants' has an incorrect structure. It should contain a single directory hierarchy for source files, named 'antspkg', but file 'language_yaml.nim' is in a directory named 'ants' instead. This will be an error in the future.
      Hint: If 'ants' contains source files for building 'ants', rename it to 'antspkg'. Otherwise, prevent its installation by adding `skipDirs = @["ants"]` to the .nimble file.
  Verifying dependencies for ants@0.3.10
       Tip: 3 messages have been suppressed, use --verbose to show them.
     Error: Unsatisfied dependency: nim (<= 1.6.10)

Expected Output

No response

Possible Solution

No response

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions