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#33874 - Suggestion for help resolve the build loop
Attached to Project:
Pacman
Opened by Daniel YC Lin (dlin) - Friday, 15 February 2013, 10:16 GMT
Last edited by Allan McRae (Allan) - Friday, 15 February 2013, 14:47 GMT
Opened by Daniel YC Lin (dlin) - Friday, 15 February 2013, 10:16 GMT
Last edited by Allan McRae (Allan) - Friday, 15 February 2013, 14:47 GMT
|
DetailsSummary and Info:
I'm porting Arch Linux to other CPU. So, there is only limited binary packages ready. I found there are makedepend/depend loop on these packages: gobject-introspection gdk-pixbuf2 librsvg cairo I think the solution for build these packages is providing some PKGBUILD.<n> file in the same directory. Like gobject-introspection/PKGBUILD # for normal build script with all arch linux binary package support gobject-introspection/PKGBUILD.1 # disable the dependency of cairo & --disable-doctool So I could 'makepkg -p PKGBUILD.1' then build a gobject-introspection package. I found most such loop caused by 'document', if PKGBUILD developers keep their build experience on such files will simplified try-and-error process. And more one day we could setup a build script to build all packages automatically. see discussion on: https://bbs.archlinux.org/viewtopic.php?pid=1232439#p1232439 |
This task depends upon