From owner-freebsd-ports@freebsd.org Tue May 30 17:44:28 2017 Return-Path: Delivered-To: freebsd-ports@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 CE840B950CB for ; Tue, 30 May 2017 17:44:28 +0000 (UTC) (envelope-from beckman@angryox.com) Received: from nog2.angryox.com (nog2.angryox.com [70.164.19.85]) by mx1.freebsd.org (Postfix) with ESMTP id A6547726FF for ; Tue, 30 May 2017 17:44:28 +0000 (UTC) (envelope-from beckman@angryox.com) Received: by nog2.angryox.com (Postfix, from userid 1001) id A967117448A8; Tue, 30 May 2017 17:37:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=angryox.com; s=powerfulgood; t=1496165846; bh=M/XGJ931v7ETKrNImvENk+T2c5W0wFTo3a9g9pmwRCs=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=IIQdLv3pUa/DiEeqpYwOHrq5w0k9Y+wM1lexqPt8f2rkZSY5Aef1eWQdioRy8YTDG fpdWNk02kQl0UBKDqIQse9WDGBI7rjzUfHvGXXp+0+44pgz7LrPbyn1OSxektmBi0h joXgYk8aEkoxdrL+RSu//CdX3Wg4D8YcQYdrBU58= Received: from localhost (localhost [127.0.0.1]) by nog2.angryox.com (Postfix) with ESMTP id A3FF517448A7; Tue, 30 May 2017 13:37:26 -0400 (EDT) Date: Tue, 30 May 2017 13:37:26 -0400 From: Peter Beckman To: Adam Weinberger cc: mexas@bris.ac.uk, rollingbits@gmail.com, freebsd-ports@freebsd.org Subject: Re: The future of portmaster In-Reply-To: Message-ID: References: <201705301415.v4UEFNJv049083@mech-as222.men.bris.ac.uk> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 17:44:28 -0000 On Tue, 30 May 2017, Adam Weinberger wrote: > You don't need separate port trees. The idea is to use poudriere to build > ALL your ports. Just make a list of the ports you want, pass it to > poudriere, and it will keep everything up-to-date, rebuild things when > they need to be rebuilt, and give you a pkg repository so you can just > run "pkg install foo" or "pkg upgrade" to keep your system running. > > Even if you do use poudriere to build only a few ports, it's pretty easy. > Give your own generated packages a higher priority in > /usr/local/etc/pkg/repos/ and you can transparently layer your pkg repo > above the upstream repo. Where is this seemingly super easy process documented? Yes, I can read the docs and try to figure out the "best practice" workflow, or someone with amazing knowledge of poudriere (and/or synth) can write a "here's how to manage your ports" best practices for the occasional sysadmin, rather than the hard-core supporting a fleet of FreeBSD boxes admin. I've looked before and never found such a document. Something from the portupgrade or portmaster user POV, and why and how to move to the more modern and actively developed tools. > So no, you don't need separate ports trees. poudriere is happiest though > when you let it manage its own ports tree, so I prefer to just symlink > /usr/ports to it, but you can very easily use a pre-existing ports tree > with poudriere. You make it sound so easy! Maybe it is, but I haven't found it. Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------