pmbootstrap-meow/pmb/aportgen
Newbyte d63ea90f2b
aportgen: Allow retaining current branch when forking Alpine (MR 2271)
Often I find myself confused and subsequently frustrated by the
behaviour of --fork-alpine as usually I apply whatever changes I want to
the aports package before forking. This is due to that in the proper
aports repo I can leverage the full power of git and apply patches or
revert commits, whereas after the package has been forked to pmaports
the context git needs to do this is lost.

To fix that, this commit introduces --fork-alpine-retain-branch which
works the same way as --fork-alpine except it doesn't change the aports
branch to match the current channel.
2024-03-17 18:36:36 +00:00
..
__init__.py aportgen: remove binutils 2023-12-03 20:11:31 +01:00
busybox_static.py aportgen: build gcc-x86_64 etc. pkgs for aarch64 2023-12-03 20:11:31 +01:00
core.py aportgen: Allow retaining current branch when forking Alpine (MR 2271) 2024-03-17 18:36:36 +00:00
device.py aportgen: Set pkgver for devices to 1 by default (MR 2275) 2024-03-11 11:54:26 -07:00
gcc.py aportgen: build gcc-x86_64 etc. pkgs for aarch64 2023-12-03 20:11:31 +01:00
grub_efi.py aportgen: use pmb.build.init_abuild_minimal 2023-06-15 08:30:54 +02:00
linux.py pmb.aportgen.linux: Depend on findutils 2023-03-12 17:20:55 +01:00
musl.py aportgen: build gcc-x86_64 etc. pkgs for aarch64 2023-12-03 20:11:31 +01:00