From owner-freebsd-ports@freebsd.org Wed May 31 17:28:45 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 40B81B7EDE3 for ; Wed, 31 May 2017 17:28:45 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "neonpark.inter-sonic.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0357884030 for ; Wed, 31 May 2017 17:28:43 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at Intersonic AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intersonic.se; s=INTERSONICSE; t=1496251720; bh=ms4ip7UPxbthUxcvVtZTSEv/vXQxOL2IlernCNNNzwA=; h=Subject:References:To:From:Date:In-Reply-To; b=ElCVAmvSrJzLdPO4FTzT8MUbA6P5AHySLBANraiHm89p95ZaaUbFiRMcDOuH7y211 nBnfW/+GgZ0+FnfALWLkAgAdX8xOSMlR1c9iz+QM+rXStXiBgttdxz2lZzY5YB3qV1 9wKR85TBhvCAWQ6ABqQ8P/Fleq1UFQOR2h0dDaBY= Subject: Re: The future of portmaster [and of ports-mgmt/synth] References: <589B133C-0175-4DD2-8847-5A3E0E697B36@dsl-only.net> <20170530200629.GA10517@lonesome.com> <20170530215306.GB11098@lonesome.com> To: FreeBSD Ports From: Per olof Ljungmark Organization: Intersonic AB Message-ID: Date: Wed, 31 May 2017 19:28:38 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Wed, 31 May 2017 17:28:45 -0000 On 2017-05-31 02:10, Kevin Oberman wrote: > On Tue, May 30, 2017 at 2:53 PM, Mark Linimon > wrote: > > On Tue, May 30, 2017 at 11:46:46PM +0200, Per olof Ljungmark wrote: > > Hello, I have not followed this thread before but just wanted to say > > that I use portmaster extensively, it works for us and I would miss > > it if it went. Are there actually plans to retire it? > > To reiterate the status: > > * some extensive changes to the ports framework are coming; > * these will require large changes to all the port upgrade tools; > * no one has stepped forwards to offer to do the work for anything > other than poudriere AFAIK. > > If no one does the work, at the time the large changes come, the > other tools will break. > > People have been wanting subpackages (aka flavors) for many years; > IIUC these are parts of the changes that are coming. > > Someone needs to step forwards and say "yes, I will do the work." > > mcl > > > Since portmaster is still popult and since the only solutions that looks > to be available in the near term are pouderiere or raw make, neither > terribly viable for many, I will look into updating portmaster to deal > with 'flavors'. This looks fairly straight forward and I my have the sh > capability to manage it. (And then again, I am far from a great shell > person, so I may well be wrong.) I have looked at Doug's script and it > is pretty readable, but writing may require help. > > Can someone point me where to look for documentation on flavors? I have > poked around the wiki, but to no avail. Unless there is documentation on > what needs to be done, doing it will be hopeless and waiting for the > packaging system to updated means portmaster WILL be broken for some > period of time. Let me just say that I would really, really appriciate if we could keep such a simple tool. Why does it suit us? Because we have a limited number of systems, and they are all different meaning that we custom build for almost every task. Portmaster makes very easy to build what we need on each host. Yes, it brakes sometimes but it is not that hard to figure out how to get around.