This repository has been archived by the owner. It is now read-only.

Streamline repo scripts #970

Open
ollieparanoid opened this Issue Dec 2, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@ollieparanoid
Member

ollieparanoid commented Dec 2, 2017

I'm building the packages for the binary repo manually. The repo is enabled by default in pmbootstrap (disable with --mirror-pmOS="") and it is somewhat usable now and it's a big improvement over having no binary packages at all. But it still needs improvements.

  • Change pmbootstrap aportgen to generate gcc-aarch64 etc. not for arch=all (9f67467)
  • use --strict for building
  • improve the building script: don't use pmbootstrap directly, wrap it with a different config and work path, so the same PC can be used for quickly testing a build without messing with the repo
  • polish repo build scripts and publish them (done: pmOS-repo-scripts)
  • properly delete old packages (#1306)
  • use proper repo description with pmbootstrap commit hash
  • use -9 compression for gzip packages (new pmbootstrap parameter)
  • Firmware packages: download blobs after installation, so we can build firmware packages, too (right now they don't get built) (#797)
  • Some packages will still build despite the same version being on the binary repo (#955)
  • add pmbootstrap build --all to simply build all packages?
  • build everything for x86, too (we do have a x86 device now!)
  • figure out a good process to (manually) update packages, with maintainers for packages etc?
  • set up a postmarketOS version of https://pkgs.alpinelinux.org aka alpine-turbo
  • create build logs for every build and upload them somewhere, so they can be linked from alpine-turbo

and finally (future!):

  • automatize it completely: whenever a new commit comes in to master, run the build

@ollieparanoid ollieparanoid self-assigned this Dec 2, 2017

ollieparanoid added a commit that referenced this issue Jan 20, 2018

Don't compile cross-compiler packages for the host arch
Example: Building gcc-armhf for armhf does not make sense, so this
commit changes arch="all" to arch="aarch64 x86_64". This helps to
simplify the repository scripts (#970).

ollieparanoid added a commit that referenced this issue Jan 24, 2018

Fix pmbootstrap zap -m / various zap improvements
zap -m:
* APKINDEX parsing: parse the "origin" field as well, so we know
  where a subpackage comes from
* pmbootstrap zap -m: properly delete all packages, that do not
  have an aport or where the aport has another version. This also
  works with subpackages now,
  we use the origin field to resolve it.
* Only reindex when packages have been deleted in "zap -m"

zap in general:
* Show the amount of cleared up space after the deletion instead
  of "Done"
* Print "Shutdown complete" to "pmbootstrap log" instead of stdout
  (we need to call it twice during zap now to get the space
  calculation right)
* Add `--dry` argument to `pmbootstrap zap` (this was very useful
  for debugging) to list the packages/chroots that would get
  deleted
* Roughly output the command that would get executed to delete
  files, so it's obvious what's going on in --dry mode. (% rm ...)

This PR relates to streamlining the binary repository (#970),
because it makes it possible to delete outdated packages properly.

PureTryOut added a commit that referenced this issue Feb 21, 2018

Don't compile cross-compiler packages for the host arch
Example: Building gcc-armhf for armhf does not make sense, so this
commit changes arch="all" to arch="aarch64 x86_64". This helps to
simplify the repository scripts (#970).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.