Date: Sat, 4 Apr 2020 19:41:54 -0400 From: Robert Huff <roberthuff@rcn.com> To: Jonathan Chen <jonc@chen.org.nz> Cc: ajtiM <starikarp@dismail.de>, freebsd-ports@freebsd.org, Serpent7776 <serpent7776@gmail.com> Subject: Re: qt5-webengine Message-ID: <24201.6978.579552.849799@jerusalem.litteratus.org> In-Reply-To: <CAJuc1zNPwat8E4d03h=rUVA-Lw0AwqJYC5uSioUjJKRXDHU4HA@mail.gmail.com> References: <20200404101044.76e34919@dismail.de> <20200404142103.GA74752@elch.exwg.net> <20200404111553.6511f6ac@dismail.de> <20200404173325.6b156762@DaemONX> <20200404144231.0d05bdf1@dismail.de> <CAJuc1zNPwat8E4d03h=rUVA-Lw0AwqJYC5uSioUjJKRXDHU4HA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan Chen writes: > Frankly speaking, if you're compiling your own ports, you > have to use either synth or poudriere; anything else will cost you > time hunting down broken dependencies. Speaking as someone who's been compiling from ports for at least a decade, and maintains 1200+ ports on at least one box: Yes ... but not much. I use portmaster and stuff mostly Just Works(tm). [Thanks, guys!] Ports get updated regularly, and the last major problem I can remember had to do with defauly version bumps in perl and python (2->3). I understand there are folks for whom poudriere or synth are The Right Tool(tm). But I am one of a number of folks for whom it is like carpet-bombing the neighborhood to get rid of one miscreant squirrel. Respectfully, Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24201.6978.579552.849799>