| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Signed-off-by: Allan McRae <allan@archlinux.org>
|
| |
|
|
|
|
|
|
|
|
| |
The return value was being assigned when an error was found in a PKGBUILD's
arch array but it never was returned.
Also remove error message explaining about adding the arch array to a PKGBUILD.
That was added a long time ago when the arch array first became compulsory.
Signed-off-by: Allan McRae <allan@archlinux.org>
|
| |
|
|
|
|
|
|
| |
When extracting variables from PKGBUILD (e.g. for .SRCINFO creation) we make
assumptions about whether variables are arrays or not. This adds a check to
the PKGBUILD linter to ensure variables are arrays or not as appropriate.
Signed-off-by: Allan McRae <allan@archlinux.org>
|
| |
|
|
|
|
| |
pkgbase should be subject to the same restrictions as pkgname
Signed-off-by: Allan McRae <allan@archlinux.org>
|
| |
|
|
|
|
|
|
| |
The check that pkgver is non-empty done in check_pkgver should also be
performed after running the pkgver() function. Merge validate_pkgver
into check_pkgver and run check_pkgver after updating pkgver.
Signed-off-by: Allan McRae <allan@archlinux.org>
|
|
|
Signed-off-by: Allan McRae <allan@archlinux.org>
|
