Sponsor:

Your company here, and a link to your site. Click to find out more.

go_vendor_archive_create - Man Page

Create reproducible Go vendor archives

Synopsis

go_vendor_archive create [Options...] PATH

Options

PATH

Path for which to create a vendor archive.

Can be one of the following:

  1. Go source tree with a go.mod file
  2. Path to a (compressed) tar archive
  3. Path to a specfile. SOURCE0 will automatically be unpacked.
--config PATH

Path to config file

--write-config

After creating the archive, write out a config file based on the CLI options

-O OUTPUT, --output OUTPUT

Output path for the vendored tarball. When PATH is a specfile, the name of SOURCE1 will be used as the output if one is not explicitly specified. Otherwise, ./vendor.tar.bz2 is the default.

-p / --use-module-proxy, ā€‰--no-use-module-proxy

Whether to use the Google Go module proxy. Defaults to true or whatever is set in go-vendor-tools.toml.

-I, ā€‰--idempotent

Only generate archive if OUTPUT does not already exist

--compression COMPRESSION TYPE

Compression type, such as tar (uncompressed), gz, bz2, or zstd. By default, the compression type is detected based on OUTPUT's extension.

--compresslevel COMPRESSLEVEL (int)

Compression level as an integer for compression algorithms that support the setting

Author

go-vendor-tools is maintained by Maxwell G and the Fedora Go SIG <golang@lists.fedoraproject.org>. See <https://fedora.gitlab.io/sigs/go/go-vendor-tools> for more information about go-vendor-tools.

See Also

go_vendor_archive(1), go_vendor_archive_override(1), go-vendor-tools.toml(5)

Referenced By

go_vendor_archive(1), go_vendor_archive_override(1).

2024-04-12