Skip to content

"mvdan.cc/sh/v3: no Go source files" on go get #703

Closed
@zikaeroh

Description

@zikaeroh

I did an update in a project that uses this module; my handy update script just requests each directly required module @latest. The recent addition of a package at the top level without any buildable files (since the one file is guarded by a build tag) makes go get unhappy:

$ go get -d mvdan.cc/sh/v3@latest              
mvdan.cc/sh/v3: no Go source files

Does the root directory need an unguarded file to ensure that the package is buildable, or maybe have its code moved to some other directory?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions