[ change ] Replace WASM git submodules with cabal source-repository-package for network

Author: banacorn

.github/workflows/wasm.yaml

@@ -21,7 +21,6 @@ jobs:
     - uses: actions/checkout@v4
       with:
         path: als
-        submodules: true
 
     - name: Compute cache key
       run: echo "CI_CACHE_KEY=${{ runner.os }}-${{ runner.arch }}-${{ env.GHC_WASM_META_COMMIT_HASH }}-flavor-${{ env.GHC_WASM_META_FLAVOUR }}" >> "$GITHUB_ENV"
@@ -109,11 +108,7 @@ jobs:
     - name: Build dependencies
       working-directory: './als'
       run: |
-        # Setup network submodule autotools
-        cd wasm-submodules/network
-        autoreconf -i
-        cd ../..
-        # Build all dependencies (cabal git deps + network submodule)
+        # Build all dependencies (all from cabal git deps and Hackage)
         wasm32-wasi-cabal build --dependencies-only
 
     - name: Build als

.gitmodules

@@ -1,10 +1,9 @@
 # How to build for WASM
 
 1. Setup a working ghc (tested with v9.10) with WASM backend and wasm32-wasi-cabal.
-2. `cd` into `wasm-submodules/network` and run `autoreconf -i`.
-3. In the project root, run `cp cabal.project{.wasm32,}`, and then `wasm32-wasi-cabal build`.
+2. In the project root, run `cp cabal.project{.wasm32,}`, and then `wasm32-wasi-cabal build`.
 
-Note: This project uses a hybrid approach - most dependencies use cabal's git handling, but the network package remains as a git submodule due to autotools requirements.
+Note: This project uses cabal's `source-repository-package` declarations to fetch git dependencies instead of git submodules.
 
 The process might output the following:
 

BUILDING_WASM.md

@@ -1,6 +1,5 @@
 packages:
   .
-  wasm-submodules/network
 
 source-repository-package
   type: git

cabal.project

@@ -1,6 +1,5 @@
 packages:
   .
-  wasm-submodules/network
 
 source-repository-package
   type: git