d8591dd341
Currently this seems to be only theoretically useful. The most likely reason for wanting a packagelist is in order to script makepkg and derive the filenames for the packages we want to install or repo-add, but in the current implementation this requires a lot of additional post-processing which must be duplicated in every utility to wrap makepkg. - It is of minimal use to know what packages might get created on some other device utilizing a different CPU/OS architecture, so don't list them. - It is non-trivial to reimplement makepkg's logic for sourcing any of several makepkg.conf configuration files, then applying environment overrides in order to get the PKGDEST and PKGEXT, so include them directly in the returned filenames. - Output is delimited by newlines, for readability. For maximum parsing reliability, libmakepkg needs to learn how to lint the PKGDEST and PKGEXT variables to ensure they do not contain newlines, which will be submitted in a separate patch. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org> |
||
|---|---|---|
| .. | ||
| completion | ||
| libmakepkg | ||
| library | ||
| po | ||
| .gitignore | ||
| Makefile.am | ||
| makepkg-template.pl.in | ||
| makepkg.sh.in | ||
| pacman-db-upgrade.sh.in | ||
| pacman-key.sh.in | ||
| pkgdelta.sh.in | ||
| repo-add.sh.in | ||
| wrapper.sh.in | ||