Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A archiso
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch Linux
  • archiso
  • Issues
  • #162
Closed
Open
Created Jan 13, 2022 by nl6720@nl6720Developer

Implement multistage bootstrapping

mkarchiso relies on multiple commands on the system that runs mkarchiso. E.g mkfs.fat, mksquashfs, mkfs.ext4, xorriso, coreutils, etc.

These software can greatly affect reproducibility. To ensure some consistency, we should record the used package versions on the system that runs mkarchiso. To do that we'd need to limit the scope of package versions to record otherwise it could become a privacy issue for people running mkarchiso. Doing so, though, would be error prone.

A solution suggested by @klausenbusk is multistage bootstrapping. I.e. create an Arch container with the required packages and run mkarchiso from there. This would be fully reproducible.

If implemented well, this could even allow running mkarchiso from other Linux distros.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking