lima-vm / lima-vm/lima

Add tarball with git submodules similar to tarball with go mod vendor

Open
#5,265 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
21.9k
Forks
957
Avg merge
2d 6h
Merged PRs (30d)
53

Description

### Description

The current Lima source tarball does **not** include the submodules:

```
[submodule "hack/bats/lib/bats-core"]
path = hack/bats/lib/bats-core
url = https://github.com/bats-core/bats-core.git
branch = master
[submodule "hack/bats/lib/bats-file"]
path = hack/bats/lib/bats-file
url = https://github.com/bats-core/bats-file.git
branch = master
[submodule "hack/bats/lib/bats-assert"]
path = hack/bats/lib/bats-assert
url = https://github.com/bats-core/bats-assert.git
branch = master
[submodule "hack/bats/lib/bats-support"]
path = hack/bats/lib/bats-support
url = https://github.com/bats-core/bats-support.git
branch = master
```

But we could export them to an "add-on" archive, on top of the other.

Like we are already doing with the go modules, in go-mod-vendor.tar.gz

Maybe also export `.gitmodules` and `git submodule status` to the archive?

Like we are including `go.mod` and `go.sum`, with the `vendor` archive.

Contributor guide

Open the contributing guide

Research direction

Start by examining how go-mod-vendor.tar.gz is produced and how the current source tarball is assembled. Review the listed submodule paths, .gitmodules, and git submodule status to determine the archive contents. Done means an add-on archive includes the submodules and the intended metadata alongside the source tarball.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, go
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.