* prepare: always patch RPM mkspec
Like this we can notice earlier if it doesn't apply any longer
Otherwise I only test RPM when issues get openned
* RPM: fix RPM mkspecp atch, thanks @W3sG for the heads up!
- Only part of the patch was applying
- Fixed also the fact that packages conflict because of
unneeded build-id files in /usr/lib/.build-id
- Removed all the hardening flags Fedora uses by default
"we do not do that here"
Fixes: #669#609
* install.sh: uninstall-help: fix Fedora query for installed TKG packages
* install.sh: RPM: fix typo in variable
Used the non absolute path for the work folder x)
* customization.cfg: add new entries for kernel paths
Two choices:
- Where to put git bare repository,
- Will be implemented as a bare repository, the folder will have only
compressed blobs and will be around ~400MB. Should be good to have
even in HDDs
- This is meant to be in a permanent storage like HDD or SSD.
But some uses could have it on a tmpfs if the storage is very slow
when compared to a full git (shallow) clone
- Where to have the work/build folder
- This will be implemented through a git worktree,
where the bare repo will be decompressed. This is best on a tmpfs folder
but needs >=32GB for a full kernel build. Otherwise should be okay with
modprobed-db
* customization.cfg: remove obsolete entries
the tmpfs related entries can be set with the previously added entries,
i.e. _kernel_work_folder and _kernel_source_folder
* prepare: check if obsoleted vars get set, warn if so and exit
Like this users will get notified about the change and act accordingly
* prepare: remove unused kernel subver patching code
this used to bump from kernel x.y to x.y.z
* prepare: add func to define kernel abs paths
We will use these absolute paths to refer to kernel folders (work and source)
* prepare: rewrite git fetching code
- Rename to "_setup_kernel_work_folder"
- Now we simply fetch directly the "commit hash" / "git tag"
from the user chosen remote, no branches
- The source folder (the one that is preferably on disk) is only a bare repo
with a small size (~400MB)
- The work folder is then (re)created / updated (as need) as a git worktree
* prepare: tkg_patcher: embed patch name into the message
Otherwise it doesn't work on the install.sh approach,
which reimplements a simple msg2 function that doesn't support %s
replacement
* PKGBUILD: use new path variable for work folder
* install.sh: use new path variable for work folder
* CI: setup source and build folder in /tmp
* prepare: update diffconfig with new kernel work folder var
- Enforce sane defaults for ticks selector
- Make sure we have a default governor set early on (schedutil)
- Build BLK_DEV_LOOP as module instead of builtin
Reportedly fixes https://github.com/Frogging-Family/linux-tkg/issues/665 for at least one user affected.
It'll require ~20GB of space by itself, so if your tmpfs is in RAM, make sure you have enough free, and it's definitely not recommended to use this on a <32GB RAM machine.
