| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Aloow overrid sharedir with global ABUILD_SHAREDIR so we test the local
functions.sh instead of a system installed functions.sh
|
|
abuild uses datadir as local variable in various functions. Rename the
global datadir to sharedir to avoid confusion.
|
|
GitHub allows to reference https://github.com/<user>/<proj>/archive/<ver>.tar.gz
also as https://github.com/<user>/<proj>/archive/<ver>/<anything>.tar.gz.
|
|
This forces cargo to install the exact versions of the dependencies
specified in Cargo.lock. This is essential for reproducible builds!
|
|
|
|
They normally don't need the python3-dev.
|
|
Seeing as the default python build/check/package apkbuild functions call `setup.py` and that relies on `py3-setuptools`, perhaps it should be added to the makedepends.
Inspiration from https://github.com/alpinelinux/aports/pull/7641#pullrequestreview-234326397
|
|
|
|
These are strings after all and should be quoted even if not strictly necessary because of tradition excluding spaces from package names.
|
|
|
|
Add a '# Check sections' comment, for consistency with the equally
commented build and package sections.
|
|
Since the obsolete 'cd "$builddir"' statements have been removed in [1],
build(), check() and package() can generate empty functions if no build
system is specified or if there is no default for the given build
system. newapkbuild will then fail, as it tries to parse the script it
generated:
$ cd /home/pmos && newapkbuild test
/usr/bin/abuild: /home/pmos/test/APKBUILD: line 18: syntax error: unexpected "}"
$ cat test/APKBUILD
...
build() {
}
...
Fix this by placing ":" in functions that would be empty.
[1]: f83d19ce79ab9f2dcc5238346a910cd18ae0f330
|
|
Since `$builddir` is officially supported and abuild automatically cd's to `$builddir`, it does not need to be part of the template anymore.
|
|
ref https://github.com/alpinelinux/abuild/pull/42
|
|
|
|
`setup.py check` does not run package tests, it performs just some check
of the package metadata. The correct command is `setup.py test`.
|
|
Changes:
* argument sanity checks:
* `PKGNAME[-PKGVER] | SRCURL`
* check if missing
* check if specified more than once (see below)
* specifying more than one buildtype flag
* `-n` (set pkgname) without using SRCURL as last argument
* `-s` (sourceforge source) without using PKGNAME as last argument
* Typo fix: exist -> exists
* `usage()`:
* always print PKGNAME and PKGDESC (instead of NAME and DESC,
NAME was used in one place and PKGNAME in another)
* link to <https://spdx.org/licenses/>
* `-m` (meson) flag was missing in short usage line at the top
* indicate that the buildtypes are exclusive
* `-c` flag: remove "to new directory" wording to make the
message shorter (this should be obvious)
* remove empty line at the end
NOTE: Before this commit, the `PKGNAME[-PKGVER] | SRCURL` was allowed
to be specified more than once, and the code looped over the arguments.
But this was not documented in `usage()` and had unexpected results:
```
$ newapkbuild first second third
$ tree
.
___ first
___ APKBUILD
___ first
___ ___ APKBUILD
___ ___ first
___ ___ ___ APKBUILD
___ ___ ___ src
___ ___ src
___ src
```
|
|
unpack will no longer unpack without a checksum, even with -f. This
means that newapkbuild will not be able to deduce what kind of build
system is contained within, so the templates for CMake, Perl, etc are
never used.
This patch ensures checksumming is done right after fetch, so that
unpack works properly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It is documented in the help output but didn't work because getopts(1)
didn't check for that option. I am assuming the person who added cmake
support simply forgot to adjust the getopts line.
|
|
|
|
Some CMake packages do not have cmake/ directory, but all have
CMakeLists.txt present in the root directory.
|
|
|
|
|
|
Those statement are no longer needed because abuild now runs with
`set -e` by default.
See also: 36d5193776180385a39626a83241822736a5f6b8
|
|
|
|
|
|
If $sdir is not defined find writes an error message to stderr. For
example when running:
newapkbuild -n foo -a foo
You will see a find error message because no source url was provided.
This commit silences any find error message. An alternative solution
would be to not invoke find unless $sdir is set.
|
|
|
|
|
|
|
|
|
|
the _builddir should never been used bu abuild due to the _ prefix.
|
|
Do not add prepare() to new APKBUILDs in the future, as this
functionality is superseded by the addition of the default prepare
patcher in abuild.
|
|
cmake is normally able to figure it out and setting them may break
ccache.
|
|
normally not used
|
|
|
|
This is a first try that *might* work for cross-compiling packages with
an absolute bare minimum of requirements, if you're lucky.
I can't debug that part further, but the references should help with it.
|
|
|
|
|
|
|
|
|
|
|
|
|
