Skip to content

Relative Path Dependencies in Cargo Prevent Normal Use #176

@sempervictus

Description

@sempervictus

Thanks for publishing this.

Started down the rabbit hole of dependency fixing in node4j-rs and finding the same thing here: these libraries can't really be used as-is because they point to relative FS paths for their deps. Any chance you might be able to update the crate references to the full git URLs (ideally against tags or commit hashes to pin for compile stability)? Can PR something to that effect but dont want to bike-shed all over your commit history :)

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