On Tue, May 10, 2016 at 01:48:18PM +0000, Christian Weisgerber wrote:
> On 2016-05-09, Marc Espie <[email protected]> wrote:
>
> > So far, I've been underwhelmed by the response to proot. Seems people don't
> > get the picture yet.
>
> Probably because there has been no coherent explanation what proot
> is, how it works, and how to use it.
NAME
proot - ports chroot builder
SYNOPSIS
proot [-B chroot] [-c configfile] [-S srcroot] [key=value ...]
DESCRIPTION
proot can fill up a chroot directory for ports building usage. It will
perform a set of actions that should fill up a destination -B chroot from
the base system (or an optional -S srcroot).
[...]
By default, proot will run check_mount, devs, ldconfig, ports_subdirs,
resolv, write_mk. It will also run snapshot if a snapshot location is
provided, or locate otherwise.
(straight from the manpage, those actions are also explained)
Things are still moving a bit, but basically,
proot -B /directory_where_you_want_your_root
should do something reasonable.
I've actually been trimming my config files considerably these past
few days, as most options get sensible defaults.
