Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#19917 - PKGBUILD does not require either build or package function?
Attached to Project:
Pacman
Opened by Loui Chang (louipc) - Wednesday, 23 June 2010, 06:00 GMT
Last edited by Allan McRae (Allan) - Monday, 28 June 2010, 12:28 GMT
Opened by Loui Chang (louipc) - Wednesday, 23 June 2010, 06:00 GMT
Last edited by Allan McRae (Allan) - Monday, 28 June 2010, 12:28 GMT
|
Detailsmakepkg will produce a package from a PKGBUILD without either a build or package function defined.
This results in an empty package with just .PKGINFO. I suppose this could have its uses. Perhaps the PKGBUILD spec (man page) could be more explicit about which items are required and which are optional for clarity. |
This task depends upon
Closed by Allan McRae (Allan)
Monday, 28 June 2010, 12:28 GMT
Reason for closing: Not a bug
Additional comments about closing: This is the intended and documented behaviour
Monday, 28 June 2010, 12:28 GMT
Reason for closing: Not a bug
Additional comments about closing: This is the intended and documented behaviour
---
pkgname=NAME
pkgver=1
pkgrel=1
arch=('any')
---
>BUILD() FUNCTION
> In addition to the above directives, the optional build() bash function usually comprises the remainder of the PKGBUILD.
>PACKAGE() FUNCTION
> An optional package() function can be specified in addition to the build() function.