Date: Sat, 17 Dec 2016 11:25:20 +0100 From: Dave Cottlehuber <dch@skunkwerks.at> To: freebsd-ports@freebsd.org Subject: Re: The ports collection has some serious issues Message-ID: <1481970320.3226425.821927745.488CB138@webmail.messagingengine.com> In-Reply-To: <1612160725340.3123@mx5.roble.com> References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> <f35be27a-67b9-27a6-1350-69a65b7b9435@FreeBSD.org> <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> <1612160725340.3123@mx5.roble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 Dec 2016, at 16:34, Roger Marquis wrote: > If portmaster was part of base I'd agree that it should be deprecated, > however, being a port it can be afforded more leeway. All portmaster > needs IMO is a strong WARNING message to be displayed on installation A) > enumerating some of the potential bugs and B) clarifying that portmaster > is third party software that is neither actively maintained nor > supported (or recommended?) by FreeBSD. > > Roger ^ this ^ The key thing that needs to change for newcomers (as a recent one myself) is to give a clear & simple recommendation in the Handbook.. not in ports or whatever after you've sifted the internet looking for more information - the implications of choosing pkg quarterly vs pkg latest, vs poudriere, portmaster etc is not at all clear - it's hard to know what is project supported vs community supported - knowing that e.g. DFLY uses synth exclusively now, and the the FreeBSD build cluster uses poudriere, gives a warm fuzzy feeling Some illustrative use cases are: - sysadmin for servers - personal user who needs custom options I was lucky to run into the first poudriere episode from bsdnow.tv and went with that from the get-go. synth's documentation is superb and keeps getting better. Both are excellent tools. A+ Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1481970320.3226425.821927745.488CB138>