From owner-freebsd-current@freebsd.org  Sun May 29 16:34:06 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A2CBB5330B
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 29 May 2016 16:34:06 +0000 (UTC)
 (envelope-from tim@kientzle.com)
Received: from monday.kientzle.com (kientzle.com [142.254.26.11])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 68BD512A8;
 Sun, 29 May 2016 16:34:05 +0000 (UTC)
 (envelope-from tim@kientzle.com)
Received: (from root@localhost)
 by monday.kientzle.com (8.14.4/8.14.4) id u4TGXw07046931;
 Sun, 29 May 2016 16:33:58 GMT (envelope-from tim@kientzle.com)
Received: from [192.168.2.102] (192.168.1.101 [192.168.1.101])
 by kientzle.com with SMTP id qa8irz9ve5agnhgj2g82fevjxi;
 Sun, 29 May 2016 16:33:58 +0000 (UTC)
 (envelope-from tim@kientzle.com)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: pkg chroot issues?
From: Tim Kientzle <tim@kientzle.com>
In-Reply-To: <8886a4b1-492b-61ea-90ea-7e694311d03b@freebsd.org>
Date: Sun, 29 May 2016 09:33:57 -0700
Cc: "bapt@freebsd.org" <bapt@freebsd.org>,
 FreeBSD current <freebsd-current@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <07425DF9-AD45-49FD-AC9B-DEF39BDAA10E@kientzle.com>
References: <9BC1A0E1-696D-4C00-B8C8-B57C4DB3A8EF@kientzle.com>
 <20160522203108.GE11189@ivaldir.etoilebsd.net>
 <20160522203243.GF11189@ivaldir.etoilebsd.net>
 <8886a4b1-492b-61ea-90ea-7e694311d03b@freebsd.org>
To: Julian Elischer <julian@freebsd.org>
X-Mailer: Apple Mail (2.3124)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 29 May 2016 16:34:06 -0000


> On May 29, 2016, at 8:55 AM, Julian Elischer <julian@freebsd.org> =
wrote:
>=20
> I was thinking that in order to do this properly the chrooted child =
should do all it's fetch requests etc via the non-chrooted parent, but =
that would have probably been a bit too complicated. (including add =
requests)

How complex would it be to perform all of the fetch requests before =
chroot?

Tim