Stream: git-wasmtime

Topic: wasmtime / issue #3808 Release source code with submodules

Wasmtime GitHub notifications bot (Feb 16 2022 at 11:05):

pinicarus opened issue #3808:

Feature

For distribution package managers, its a lot easier if each upstream release provides a consolidated source code archive.

Currently the main wasmtime project needs at least the WASI, crates/wasi-nn/spec and crates/wasi-crypto/spec git submodules to properly compile but these do not provide matching release source code archives.

A simple github/workflows task could easily consolidate all submodules into a single archive, as done e.g. by the wabt project.

Benefit

Each release provides a consolidated source code archive, that in turn makes it simpler to provide distribution packages built on them and spread the project to a bigger audience.

Alternatives

Each distribution package maintainer needs to fetch individual source code archive for each submodules, possibly sticking to the main branch, which may break package building unexpectedly or fixating to a specific commit, which would not include fixes until refreshed.

This is a cumbersome and error-prone way to write distribution packages, which in turn could hurt the upstream project visibility.

Wasmtime GitHub notifications bot (Feb 16 2022 at 12:15):

pinicarus edited issue #3808:

Feature

For distribution package maintainers, its a lot easier if each upstream release provides a consolidated source code archive.

Currently the main wasmtime project needs at least the WASI, crates/wasi-nn/spec and crates/wasi-crypto/spec git submodules to properly compile but these do not provide matching release source code archives.

A simple github/workflows task could easily consolidate all submodules into a single archive, as done e.g. by the wabt project.

Benefit

Each release provides a consolidated source code archive, that in turn makes it simpler to provide distribution packages built on them and spread the project to a bigger audience.

Alternatives

Each distribution package maintainer needs to fetch individual source code archive for each submodules, possibly sticking to the main branch, which may break package building unexpectedly or fixating to a specific commit, which would not include fixes until refreshed.

This is a cumbersome and error-prone way to write distribution packages, which in turn could hurt the upstream project visibility.

Wasmtime GitHub notifications bot (Feb 16 2022 at 12:16):

pinicarus edited issue #3808:

Feature

For distribution package maintainers, its a lot easier if each upstream release provides a consolidated source code archive.

Currently the main wasmtime project needs at least the WASI, crates/wasi-nn/spec and crates/wasi-crypto/spec git submodules to properly compile but these do not provide matching release source code archives.

A simple github/workflows task could easily consolidate all submodules into a single archive, as done e.g. by the wabt project.

Benefit

Each release provides a consolidated source code archive, that in turn makes it simpler to provide distribution packages built on them and spread the project to a bigger audience.

Alternatives

Each distribution package maintainer needs to fetch individual source code archives for each submodule, possibly sticking to the main branch, which may break package building unexpectedly or fixating to a specific commit, which would not include fixes until refreshed.

This is a cumbersome and error-prone way to write distribution packages, which in turn could hurt the upstream project visibility.

Wasmtime GitHub notifications bot (Aug 15 2022 at 14:27):

alexcrichton closed issue #3808:

Feature

For distribution package maintainers, its a lot easier if each upstream release provides a consolidated source code archive.

Currently the main wasmtime project needs at least the WASI, crates/wasi-nn/spec and crates/wasi-crypto/spec git submodules to properly compile but these do not provide matching release source code archives.

A simple github/workflows task could easily consolidate all submodules into a single archive, as done e.g. by the wabt project.

Benefit

Each release provides a consolidated source code archive, that in turn makes it simpler to provide distribution packages built on them and spread the project to a bigger audience.

Alternatives

Each distribution package maintainer needs to fetch individual source code archives for each submodule, possibly sticking to the main branch, which may break package building unexpectedly or fixating to a specific commit, which would not include fixes until refreshed.

This is a cumbersome and error-prone way to write distribution packages, which in turn could hurt the upstream project visibility.

Last updated: Dec 23 2024 at 13:07 UTC