- Oct 10, 2024
-
-
-
The CI started to fail cause of test timeout sometimes.
-
Natanael Copa authored
-
Natanael Copa authored
-
-
-
Sertonix authored
A newline starts a new command in shell scripts and eval uses the shell grammar. Use a space instead to fix multiline repo templates. Also avoid one subshell.
-
Pablo Correa Gómez authored
Fixes da9269ba
-
-
- Oct 09, 2024
-
-
Fixes <da9269ba> abuild: warn when files are installed to non-usr locations
-
These comments don't have any purpose. They just take up space.
-
Fixes #10147
-
-
Sertonix authored
-
Sertonix authored
-
Sertonix authored
-
When a variables is declared (with 'local' or 'export') a failing command is ignored[0]. Changing that so abuild should now error out properly in more cases. Also remove 1 pipe that could have prevented an issue recently[1] where the 'du' command core dumped but abuild didn't error. The other pipes were not changed for now since it may be better to use 'set -o pipefail' instead. That may require some changes with commands like grep which use a non-zero exit code to indicate if a match was found or similar[2]. [0]: https://www.shellcheck.net/wiki/SC2155 [1]: aports#16005 (comment 395899) [2]: https://github.com/koalaman/shellcheck/issues/665
-
-
-
- Oct 08, 2024
-
-
boost1.82 which used this variable has been removed
-
Natanael Copa authored
The term validate/validation is better than sanity/sane.
-
- Oct 07, 2024
-
-
As agreed upon by the TSC: https://gitlab.alpinelinux.org/alpine/tsc/-/blob/master/minutes/2024-08-15.md?ref_type=heads#implement-usr-merge-73 Should be changed to an error once some core packages are adjusted.
-
The setfattr/getfattr commands were not guaranteed to be available and abuild wouldn't properly error when they are not. That may cause some hidden issues. Changing the code to not need setfattr/getfattr like it is done in default_dbg ([3ad93d9a]) and pacman mkpkg ([pacman@88d054093c1]). The code works by first writing the stripped output into a temporary file and then replace the contents of the already existing file without changing any file metadata. [3ad93d9a]: alpine/abuild@3ad93d9a [pacman@88d054093c1]: https://gitlab.archlinux.org/pacman/pacman/-/commit/88d054093c1c99a697d95b26bd9aad5bc4d8e170
-
Add a reference in the SEE ALSO section. Improves discoverability of this tool for newcomers. See: alpine/lua-aports!16
-
-
-
-
By setting some environmental variables in default.conf we can reduce the amount of duplicated code needed in APKBUILDs.
-
-
This mechanism was an optional speed optimization for apk-tools which has been replaced with a better one **before the 2.0 full release** of apk-tools. This in combination with the fact that the code is endian dependant and therefor is incompatible with reproducible builds seems enough reason to remove the code.
-
This fixes 'abuild rootbld' failing to mount when srcdir is moved outside of $HOME (eg. in /run). This also has the advantage of building more reproducible even when the build path leaks into the packges (which happens in most -dbg packages).
-
These variables are already set by functions.sh.
-
I rebuilt networkmanager locally and was greeted with this: >>> Size difference for networkmanager: 16 MiB -> 2772 KiB It turns out networkmanager-elogind provides networkmanager so apk info will list both, and the former is much bigger so it looked like the rebuilt package was much smaller when there was almost no difference (as expected) Fix by matching on exact package name for both lines; this is already what we were doing with the local package anyway and the apk fetch correctly picks the correct package in this case
-
according to the meson documentation the arguments are 'meson setup <builddir> <srcdir>'. meson is very relaxed and allows the wrong order but this behavior should not be endorsed by a template.
-
dmd installs an object file that matches *.so.* so we need to check for *.o explicitly.
-
-
Closes alpine/abuild#10127
-
--unshare-pid is needed for --die-with-parent to work correctly. Ref https://github.com/containers/bubblewrap/issues/529
-
For those familiar with abuild all this content is obvious. For newcomers, the only way to figure this out is by reading abuild's source code.
-
-
