Mail archive

Re: [alpine-devel] a few abuild oddities

From: Jim Pryor <>
Date: Tue, 3 Dec 2013 22:47:11 -0500

On Tue, Dec 03, 2013 at 04:34:09PM +0100, Natanael Copa wrote:
> > Is it possible to use abuild for the full range of activities without
> > being in the abuild group? Do we just prompt with sudo or su in those
> > cases when needed? In that case the security-conscious solution will
> > just be don't add your users to the "abuild" group. The costs and
> > benefits of this would just need to be more clearly documented.
> You need either be in abuild group or have sudo permissions to use
> abuild -r for letting abuild install the deps for you.

Ok, but they don't have to be permissions to use "sudo abuild -r ..."
WITHOUT PASSWORD, correct? That's the behavior I expect.
> To use sudo instead of abuild-apk you can set SUDO_APK="sudo apk"
> in /etc/abuild.conf (or just export SUDO_APK="sudo apk").

Great, thanks.

> You can still build packages with abuild without needing sudo but then
> all the dependencies needs to be installed already:
> SUDO_APK=apk abuild
> The motivation behind abuild group was to make it convenient to set up
> a build server. Might be we want change the default back to sudo.

Received on Tue Dec 03 2013 - 22:47:11 UTC