From owner-freebsd-ports@freebsd.org Wed Feb 15 20:09:06 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 75AB7CE08E7 for ; Wed, 15 Feb 2017 20:09:06 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from anoxia.adamw.org (anoxia.adamw.org [104.225.8.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anoxia.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A52F15C5 for ; Wed, 15 Feb 2017 20:09:05 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by anoxia.adamw.org (OpenSMTPD) with ESMTPSA id 9896c4fd TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 15 Feb 2017 13:09:04 -0700 (MST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Status of synth following expulsion of John Marino? From: Adam Weinberger In-Reply-To: <58A4A95F.20303@abinet.ru> Date: Wed, 15 Feb 2017 13:09:02 -0700 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <745FB9DE-D067-4757-8916-D1028627183D@adamw.org> References: <33.4E.19143.3DE14A85@dnvrco-omsmta03> <3F2A28D7-A3A4-4549-B125-805EC9923F3B@adamw.org> <58A4A227.6080000@abinet.ru> <113653FF-1F93-448E-99C6-9943BBD9DAAE@adamw.org> <58A4A95F.20303@abinet.ru> To: abi X-Mailer: Apple Mail (2.3259) 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, 15 Feb 2017 20:09:06 -0000 > On 15 Feb, 2017, at 12:17, abi wrote: >=20 >=20 >=20 > On 15.02.2017 21:58, Adam Weinberger wrote: >>> On 15 Feb, 2017, at 11:47, abi wrote: >>>=20 >>>=20 >>>=20 >>> On 15.02.2017 18:00, Adam Weinberger wrote: >>>>> On 15 Feb, 2017, at 2:26, Thomas Mueller = wrote: >>>>>=20 >>>>> Expulsion of John Marino was a shocker to me, caught me by = surprise. >>>>>=20 >>>>> Now my question is what is the status of synth? >>>>>=20 >>>>> Should I switch from portmaster to synth? >>>>>=20 >>>>> If synth is deprecated or dropped, after I switch from portmaster = to synth, then I have to switch back, and this would be a monster mess = of extra work. >>>>>=20 >>>>> Not to be inflammatory here, just want to know where I/we stand = and don't want to go too far off course updating my ports. >>>>=20 >>>> I don't recommend portmaster for anybody. It's unmaintained, it = already causes headaches on upgrades, and even though it works now, it = is unlikely to keep working as the ports tree evolves. >>>=20 >>> This is FUD. Yes, portmaster can be less maintained, but it works = without observable issues, at least I don't see any problems with it on = my systems. synth and poudriere lacks the ability to set and maintain = port options recursively, eliminating any practical (from user = perspective, not developer) use of such software stand alone. >>=20 >> Sure it does. >>=20 >> poudriere options -j jailname editors/vim >>=20 >> Sets options recursively. >>=20 >> Not seeing any problems with it right now isn't the point of my = message. The point is that portmaster WILL break when new features = (currently in progress) are added to the ports build system, and being = unmaintained, there's no guarantees that it will ever unbreak. >>=20 >=20 > Poudriere can't be considered as an option for everyone due to it's = connection to jails, synth can't set options recursively, however it's = extremely simple to use. >=20 > According to current port tree, portmaster has maintainer and it's = simple enough to be fixed by virtually everyone. >=20 > Can you provide link to new features? Never saw that port tree has = some drastically changes. You're right, jails do require more setup, drive space, and complexity = (not to mention being quite slow on UFS). But at the end of the day, = jails are a better paradigm for building ports. Most failures these days = come from the environment influencing the build, or upgrade problems = rebuilding ports when old ports stop working haphazardly. Best effort is = taken to fix these problems, but maintainers and committers can't = predict every setup possibility; the general target is making sure that = they build in a pristine environment, meaning poudriere. = https://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D134825+0+archive/2016/free= bsd-ports/20161225.freebsd-ports for the new features I was referring = to. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org