From owner-freebsd-pkg@FreeBSD.ORG Wed Sep 10 15:34:04 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2660C17E for ; Wed, 10 Sep 2014 15:34:04 +0000 (UTC) Received: from astart2.astart.com (108-248-95-193.lightspeed.sndgca.sbcglobal.net [108.248.95.193]) (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 EC9FA1362 for ; Wed, 10 Sep 2014 15:34:03 +0000 (UTC) Received: from laptop_93.private (localhost [127.0.0.1]) by astart2.astart.com (8.14.4/8.14.4) with ESMTP id s8AFXuP8047156 for ; Wed, 10 Sep 2014 08:33:57 -0700 (PDT) (envelope-from papowell@astart.com) Message-ID: <54106F64.3050305@astart.com> Date: Wed, 10 Sep 2014 08:33:56 -0700 From: Patrick Powell Reply-To: papowell@astart.com Organization: Astart Technologies User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-pkg@freebsd.org Subject: Re: make -DNO_ROOT to create chroot, problem installing into chroot with pkg References: <20140908154858.GB35236@spindle.one-eyed-alien.net> <20140908183647.GD35236@spindle.one-eyed-alien.net> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 15:34:04 -0000 On 09/09/14 13:51, Julio Merino wrote: > On Mon, Sep 8, 2014 at 2:36 PM, Brooks Davis wrote: >> I believe the majority of packages don't suffer from post-install >> scripts hence the suggestion that extracting in the right place without >> root would solve 80-90% of the problem (and probably take no more than >> 10% of the work). I could live with the pain of not having scripts run >> during install. The correct long term fix as proposed by bapt is the do >> anyway with most scripts in favor of common actions and if any >> significant scripts remain add the ability to run them on first boot. > Cool; glad to hear. This sounds like a good plan. > _______________________________________________ > freebsd-pkg@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-pkg > To unsubscribe, send any mail to "freebsd-pkg-unsubscribe@freebsd.org" > Having dealt with 'run on first boot' installation issues, I don't think that this is a good idea. Have you ever tried to debug one of these little beasts? And make sure that the script is removed so that it does not run again? And deal with adding a whole new infrastructure to deal with this SEPARATE from the current FreeBSD configuration? I lived through the headaches dealing with startup scripts having to be added to things like /etc/rc.local and finally seeing the consensus of using /usr/local/etc/rc.d/xxxx for separate scripts... And now you want to add something like: /usr/local/etc/run_on_first_boot/xxxx? Please reconsider adding 'run on first boot' capabilities.