From owner-svn-ports-all@freebsd.org Thu Feb 4 15:56:34 2016 Return-Path: Delivered-To: svn-ports-all@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 3EF68A9BD68; Thu, 4 Feb 2016 15:56:34 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [204.109.59.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "abg.ninja", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FDB71BDD; Thu, 4 Feb 2016 15:56:33 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 395031f7 TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 4 Feb 2016 08:56:23 -0700 (MST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: svn commit: r407270 - head/ports-mgmt/portmaster From: Adam Weinberger In-Reply-To: <56B36C8A.8070503@marino.st> Date: Thu, 4 Feb 2016 08:56:22 -0700 Cc: Pietro Cerutti , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org, owner-ports-committers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3B17D597-12D7-45A7-AF5D-2A0718381B41@adamw.org> References: <201601261123.u0QBNcvL091258@repo.freebsd.org> <8b37e4951fc45b4f1eeaf5eb67f76804@gahr.ch> <56B36ACE.1010506@marino.st> <56B36C8A.8070503@marino.st> To: marino@freebsd.org X-Mailer: Apple Mail (2.3112) X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 15:56:34 -0000 > On 4 Feb, 2016, at 8:21, John Marino = wrote: >=20 > On 2/4/2016 4:18 PM, Pietro Cerutti wrote: >> Fair enough. Let's just be clear and cautious when suggesting people = to >> switch to beta software for their production needs. >=20 > To be fair, I also suggested poudriere as an alternative which is > undeniably mature. At the time, Synth was good enough for production. > I'm basically polishing now. I played around with Synth for a couple days. I really, really like it. = Once it's production ready it absolutely deserves to be written into the = handbook and taught to new users as the go-to tool for overseeing port = builds. Beyond polish, there's two things that made me not want to use it at = this point: 1) As you said in your reply to my previous extremely rude email, synth = is lightweight as long as it's installed by 'pkg install synth'. Is = there some way to mark synth as not to be built by synth? The next = 'synth upgrade-system' rebuilds synth, including gcc and all its = dependencies. It'd be nice to have a list of ports that synth will fetch = rather than rebuild. (I know that I could maintain a separate list of my = ports and use that but I'd rather maintain a list of exceptions.) Does = that make sense? 2) The big problem for me is rebuilding the repository after every = single step. My main pride & joy server is a little VM from RootBSD. = Rebuilding the repository takes about an hour. Installing a port, = upgrading a port, checking to see if there were updates and not = rebuilding anything---each of these tasks takes over an hour. At home I = have an 8-core machine with 16G of RAM and an SSD, and rebuilding the = repository takes 25 minutes. Is there some way to use synth without = having to rebuild the entire repository every time? I can't see myself = ever using it when each command takes over an hour to run. # Adam --=20 Adam Weinberger adamw@adamw.org http://www.adamw.org