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#48497 - [makepkg] match examples: PKGDEST (makepkg.conf) with [custom] (pacman.conf)
Attached to Project:
Pacman
Opened by Alad Wenter (Alad) - Monday, 07 March 2016, 20:04 GMT
Last edited by Allan McRae (Allan) - Sunday, 04 December 2022, 10:15 GMT
Opened by Alad Wenter (Alad) - Monday, 07 March 2016, 20:04 GMT
Last edited by Allan McRae (Allan) - Sunday, 04 December 2022, 10:15 GMT
|
DetailsSummary and Info:
pacman.conf has a [custom] example commented: # An example of a custom package repository. See the pacman manpage for # tips on creating your own repositories. #[custom] #SigLevel = Optional TrustAll #Server = file:///home/custompkgs makepkg.conf has PKGDEST commented as: #-- Destination: specify a fixed directory where all packages will be placed PKGDEST=/home/packages It's natural if both examples would match. I'd suggest file:///home/packages in pacman.conf, as the custom nature is already implied by the [custom] name. |
This task depends upon