On 17/4/19 3:17 am, Eli Schwartz wrote:
Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> ---
Comments from v1 indicate this will be useful for (e.g.) devtools to read a makepkg.conf. But devtools uses a custom makepkg.conf plus info from a users ~/.makepkg.conf. This patch will allow reading the custom makepkg.conf, but as it is not the system makepkg.conf it would then not parse the ~/. one. So does this patch achieve its purpose? , In devtools, there is one "pristine" makepkg.conf used for configuring
On 5/8/19 1:08 AM, Allan McRae wrote: the chroot, but we also want to extract certain variables from "whatever plain old makepkg would see". MAKEFLAGS and PACKAGER as well as the *DEST settings. As per makepkg, these could be set in /etc/makepkg.conf or in ~/. -- so the objective would be to use this function and load the default /etc/makepkg.conf + user-specific ones, and then eventually echo "MAKEFLAGS='$MAKEFLAGS'" >> $chrootdir/etc/makepkg.conf It would also be useful in another script, to obtain the $PKGDEST -- the script will run makechrootpkg on a remote build server, then scp the files back to the local machine, and it would be nice to scp it into the same directory makepkg would have used if run locally. I expect there are other programs out there which also desire to do high-level things around makepkg, while still using makepkg's configuration directories. -- Eli Schwartz Bug Wrangler and Trusted User