Skip to content

Workaround for forbidden artifact/crate names #58

Open

Description

@LukasKalbertodt

Hi there!

Unfortunately, Cargo forbids a few names for packages or artifacts. See:

I noticed this because I wanted to have a build script build.rs. This leads to:

error: failed to parse manifest at `/home/lukas/.cargo/script-cache/file-build-5b0f8f572ede70cb/Cargo.toml`

Caused by:
  the binary target name `build` is forbidden
internal error: cargo failed with status 101

I am not sure why these names are forbidden, but it would be nice if they'd work with cargo-script. For example, one could check if the name of the script is on the blacklist and then just add -cargo-script or something. When executing a script, one usually doesn't care about the actual package and artifact name.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions