From owner-freebsd-ports@freebsd.org Thu Feb 16 13:05:25 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 E2757CE1491 for ; Thu, 16 Feb 2017 13:05:25 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cdptpa-oedge", Issuer "cdptpa-oedge" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AB64B144C for ; Thu, 16 Feb 2017 13:05:25 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from [76.181.114.47] ([76.181.114.47:53460] helo=raspberrypi.bildanet.com) by cdptpa-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id A0/30-03423-153A5A85; Thu, 16 Feb 2017 13:04:17 +0000 Received: from [192.168.1.40] (helo=desktop.example.org) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1ceLjN-0003l4-1x for freebsd-ports@freebsd.org; Thu, 16 Feb 2017 08:04:17 -0500 Subject: Re: The future of portmaster To: freebsd-ports@freebsd.org References: From: Baho Utot Message-ID: <945f6d92-6834-7e2c-18c4-0a17e2c04122@columbus.rr.com> Date: Thu, 16 Feb 2017 08:04:16 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.6:25 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: Thu, 16 Feb 2017 13:05:26 -0000 On 02/16/17 06:08, Luca Pizzamiglio wrote: > Hi all, > > portmaster, a tool used/loved/hated, is almost in abandoned state. > I'm a portmaster user, because, in some cases, it fits my needs. > In other cases, I use other tools, like poudriere or synth, that are > really great. > I don't want to open a discussion here about what it's better, but the > truth is, that I use portmaster and it's not maintained. > So I decided to spend some time to look at it and to work on it. > > I forked it and I start some work. > The plan is: > - remove obsolete features, like the -PP option > - remove pkg_* support (even if someone could be against it), forcing > the usage of pkg > - prepare the support of new features like FLAVORS and subpackages > - adding a new ports, called portmaster-devel, for the new version > > I did a branch on github working of the first two points > (https://github.com/pizzamig/portmaster/tree/remove_oldpkg) > > I'm looking for constructive critics, feedbacks, anything that can > help me to make portmaster an actively maintained and used tool. > > Thanks in advance > > Best regards, > pizzamig > > PS: I won't start a port/pkg tool war, my opinion is that the world is > big enough to have poudriere, synth, portmaster, portupgrade and > whatever tool you will write to handle/build any ports package in the > way that you prefer. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > If you can have it build in a clean chroot or jail then you'll get my attention