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
  • #97
Closed
Open
Created Feb 01, 2021 by nl6720@nl6720Developer

Build ISOs in CI with the correct mkinitcpio hooks/scripts

archiso/initcpio/ should be used when building the the ISO in GitLab CI.

It doesn't matter much for now, but it will become relevant when the built ISO will be tested/used.

Based on the instructions from archiso-git:

  1. Use a custom PKGBUILD, to create mkinitcpio-archiso from archiso/initcpio/,
  2. Setup a custom local repo and add the built package to it,
  3. Add the repo as the first repo in configs/*/pacman.conf.

This could also be solved by implementing #47 (closed). Then initcpio stuff can be tested separately from mkarchiso, but that won't allow testing improvements that require changes to both.

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