| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
fix issue with how perl-dev was added as a makedepends
perl probably should be a dependency of all per modules
|
|
|
|
|
|
|
| |
aports convention is to delete empty variables from APKBUILD files
this causes and issue with updating existing APKBUILD files
new depends, makedepends or checkdepends are added to process the file
properly. Empty variables are then deleted once the file processes correctly
|
|
|
|
|
|
|
| |
remove trailing pkgver from some module names
attempt to use additional variable content to determine perl package name
this now appears to support all but 10 or 11 non metacpan api retrievable
module information and add a package mapping for perl-ldap
|
|
|
|
|
|
|
|
| |
return unique
do_depends can send multiple meta dependencies as additional parameters
parse_deps was not itterating through each of the parameters
this fix gets the entire list without duplicate entries
|
| |
|
|
|
|
| |
fixes #9984
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This is the only appearance of `apk` in the source. Appears accidental.
Fixes: 41343329 ("abuild: fix dependency tracing for cross builds")
Signed-off-by: A. Wilcox <AWilcox@Wilcox-Tech.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
This will warn then paths for certain shells that have completions are
found and tell the user to add a subpackage for it.
In a future date we also want to warn the user to move certain
directories where packages have completions to those directories so our
default_ functions can move them without problems
|
| |
|
| |
|
|
|
|
| |
This can be used to pick another tool to elevate privileges.
|
|
|
|
|
|
|
|
|
| |
This way Meson and CMake will use the C{,PP,XX}FLAGS we've set in
`/etc/abuild.conf`. Without this change CMake and meson will overwrite
our CFLAGS with custom flags. Most importantly, they prefer -O1/-O2 over
our -Os.
See also: https://lists.alpinelinux.org/~alpine/devel/%3C2896c13070c508a49cbaa72c8fb7f34ea947358b.camel%40cogitri.dev%3E
|
|
|
|
|
| |
- Call "$abuild_path" instead of plain "abuild"
- Pass $forceroot as done elsewhere
|
|
|
|
|
|
| |
CARGO_HOME tells cargo where to store installed dependencies, save it to
a directory in $SRCDEST so we don't need to download all dependencies
again when compiling a rust package.
|
|
|
|
|
| |
It is recommended by upstream CMake (it will warn when you do in-source
builds) to keep generated files away from the source.
|
|
|
|
|
|
|
| |
This makes it easier to figure out to which build the directory belongs
to. Occasionally, I have many failed abuild rootblds in my /var/tmp and
including the $pkgname in the directory would help me associating the
directories with failed builds I recently executed.
|
|
|
|
|
|
|
|
| |
Fixes the error:
df: .: can't find mount point
When running abuild inside a chroot when the root file system
mountpoint information is not necessarily directly available.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Originally "gcc -dumpmachine" was used to detect build gcc triplet.
However, abuild does not depend on gcc or build-base (but installs
it if needed to build) so gcc might not be there. Additionally
abuild-sign can be used standalone, and does not have gcc dependency.
Using ${CC:-gcc} is problematic in cross-compile, as CC might be
already set for the cross-compiler and would result giving the target
host triplet.
It was deemed simplest to use "apk --print-arch" exclusively to detect
the builder host type, or specify CBUILD manually. If there is need
to use abuild/abuild-sign on non-Alpine hosts withou apk, we can
later add fallback that uses "uname -m" to detect the architecture
and guess Alpine CBUILD from it.
Fixes #9974
Fixes: 5adf47c1 "functions.sh: use apk --print-arch for CARCH if gcc is missing"
Fixes: 95cd15c0 "functions.sh: dont die if gcc is missing"
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Previously, a key size of 2048 bits was hardcoded. While this is still
the default, it can now be changed. Additionally, the default key size
might be changed to 4096 in the future.
|
| |
|
| |
|
|
|
|
| |
fixes #9981
|
|
|
|
|
|
| |
fix patches such as https://dev.alpinelinux.org/archive/domoticz/openzwave-1.6.patch
previously it would only work with the filenamename.patch::$url syntax
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without this change abuild rootbld would fail with:
touch: invalid date '@'
Because SOURCE_DATE_EPOCH wasn't set when abuild rootbld was used. This
is a bug introduced in 71d9d5233b9db3be91510addcb28721545d93185. Instead
of reverting the aforementioned commit move the SOURCE_DATE_EPOCH
initialization to a custom function and also call it from the abuild
rootbld function.
Fixes #9978
|
|
|
|
|
|
|
| |
The introduction of the --pax-options seems to confuse apk and resulted
in `BAD archive' errors.
This reverts commit f04a2ee34b28a38c4349ef1f94686a07afce730f.
|
|
|
|
|
|
| |
abuild-sign does not use gcc.
fixes #9974
|
| |
|
|
|
|
| |
fixes !7
|
|
|
|
|
|
|
|
|
| |
Currently the permissions for abuild-sudo is set to 4111, this make it
impossible to move the sudo file after it has being created. Moving
the sudo file is needed by yocto when creating an apk-package of abuild.
The sudo binary in debian stretch since if debian does it, it can't be bad.
Signed-off-by: Fredrik Gustafsson <fredrigu@axis.com>
|
| |
|
|
|
|
|
| |
getting the commit date can be timeconsuming so only do it once we need
it. We also re-use the ABUILD_LAST_COMMIT to speed up the operation.
|
|
|
|
| |
rename the global variable to upppercase.
|
|
|
|
|
|
| |
Add -- to explicitly separate out the file path.
Let git_last_commit_epoch take an option with the hash.
|
|
|
|
|
| |
Flags to make the tarball reproducible is taken from here:
http://h2.jaguarpaw.co.uk/posts/reproducible-tar/
|