Skip to content

Remove large vendor/ sub-directory? #1283

Open

Description

@jas4711

Hi! I help maintain this for Debian, and we currently filter out the vendor/ sub-directory to avoid duplicate source copies. As far as I can tell, the standard for most Go packages I've seen is to not put copies of the dependencies into the git repository, but to rely on the Go compiler to find external packages. Would you consider removing the vendor/ top-level directory entirely? I think this would simplify code audits of your project, as one would not have to read through all external source codes which isn't really coming from this project.

Thanks,
Simon

Activity

  1. squeed commented on Oct 26, 2026

    @squeed
    Member

    @jas4711 thanks for reaching out. I don't have a strong opinion one way or the other on /vendor. Many projects keep it (Cilium, Kubernetes). Others have removed it (e.g. etcd, coredns, prometheus).

    My instinct would be to remove it. Anyone else have a thought?

  2. squeed commented on Oct 26, 2026

    @squeed
    Member

    Packagers are the unsung heroes of the linux world. Anything to make their lives easier is usually worth it, IMO.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions