X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 059F0DC009C for ; Wed, 4 Dec 2013 03:47:13 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 043BB215DB; Tue, 3 Dec 2013 22:47:11 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 03 Dec 2013 22:47:13 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=smtpout; bh=FqVOTEQ4RW3BoZZWAK2mrJJyoHU=; b=mgD7mi9OCn8iwqII0Q3UDvsjlsmt toxt8y04iaM3sZVeQp0k/VfEbaQPALIm5Te8uQ8viavxhwh7T6NYAI8PLgg8SFoU ralVGXi/L4yJoOI00mZpRQ1Trzga8Cw6iq2z093wH34Nep3Ouaf9g3Rs15264oLN DhJDpvlNKf//xZ0= X-Sasl-enc: f+WXa3ITlYt+0Ck4u8SjaCIfQAYmulQkp+IogcNtnGWn 1386128831 Received: from localhost (unknown [69.86.161.244]) by mail.messagingengine.com (Postfix) with ESMTPA id 92459680110; Tue, 3 Dec 2013 22:47:11 -0500 (EST) Date: Tue, 3 Dec 2013 22:47:11 -0500 From: Jim Pryor To: Natanael Copa Cc: Alpine Subject: Re: [alpine-devel] a few abuild oddities Message-ID: <20131204034711.GL29236@zen> Mail-Followup-To: Natanael Copa , Alpine References: <20131201174554.GB29236@zen> <20131201235659.GD29236@zen> <20131202142914.4438af81@ncopa-desktop.alpinelinux.org> <1386000265.25324.54500989.5FF25FA8@webmail.messagingengine.com> <20131203163409.2bfaef86@ncopa-desktop.alpinelinux.org> X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131203163409.2bfaef86@ncopa-desktop.alpinelinux.org> User-Agent: Mutt/1.5.22 (2013-10-16) 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. -- Dubiousjim dubiousjim@gmail.com --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---