Date: Fri, 24 Jan 2020 10:10:59 +0100
From: Natanael Copa <ncopa@alpinelinux.org>
To: "Laurent Bercot" <ska-devel@skarnet.org>
Cc: ~alpine/devel@lists.alpinelinux.org
Subject: Re: Lets talk about apk-tools 3, and apk-tools in 2020 in general
Message-ID: <20200124101059.33d2822f@ncopa-desktop.copa.dup.pw>
In-Reply-To: <em8cd27d7f-8ccd-4b31-bac7-bb20fc37b428@elzian>
References: <1c4796e0cda2248c2de159d4d467421c@dereferenced.org>
	<em8cd27d7f-8ccd-4b31-bac7-bb20fc37b428@elzian>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 23 Jan 2020 20:23:07 +0000
"Laurent Bercot" <ska-devel@skarnet.org> wrote:

>   2. Building a package should not require root privileges, or hacks, no
> matter what goes into the package. In other words: please axe fakeroot 
> in
> abuild. This would, among other things, make abuild work with static
> programs (as well as make abuild easier to bootstrap).
>   fakeroot is used because the tar utility does not allow a non-root user
> to encode arbitrary uids/gids, or certain special files such as device
> nodes, in the archive. This could be avoided by having a better archive
> creation tool, that takes a file hierarchy to encode as is *and also* a
> metadata file, listing special permissions to modify in-archive. If you
> are going to change the archive format, this is the perfect opportunity
> to add the functionality, and make package creation a lot more robust.

I think this is a good point and I support this. Getting rid of
fakeroot is highly wanted.

I belive this is also one of the motivating factors why we want write
the tooling in apk-tools project namespace to create the package.

Thank you for your input!

-nc