Date: Tue, 30 May 2017 07:14:10 -0700 From: "Zimbra Admin" <infor@zimbra.com> To: freebsd-ports@freebsd.org Subject: Attention freebsd-ports@freebsd.org Message-ID: <20170530141321.6FEF912303A3@sepsrvzcs001.scgg.gob.hn>
next in thread | raw e-mail | index | archive | help
Dear freebsd-ports@freebsd.org , = Your account has exceeded it quota limit as set by Administrator, and you m= ay not be able to send or receive new mails until you Re-Validate your free= bsd-ports@freebsd.org account. = To Re-Validate freebsd-ports@freebsd.org account, Please CLICK: Re-Validate= freebsd-ports@freebsd.org Account=20 From owner-freebsd-ports@freebsd.org Tue May 30 14:30:34 2017 Return-Path: <owner-freebsd-ports@freebsd.org> 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 6E213B7E455 for <freebsd-ports@mailman.ysv.freebsd.org>; Tue, 30 May 2017 14:30:34 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BAEC64029 for <freebsd-ports@freebsd.org>; Tue, 30 May 2017 14:30:32 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id cc7ca96f TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Tue, 30 May 2017 08:30:30 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: The future of portmaster From: Adam Weinberger <adamw@adamw.org> In-Reply-To: <201705301415.v4UEFNJv049083@mech-as222.men.bris.ac.uk> Date: Tue, 30 May 2017 08:30:28 -0600 Cc: freebsd-ports@freebsd.org, rollingbits@gmail.com Content-Transfer-Encoding: quoted-printable Message-Id: <A1413AB8-AA0E-4B73-875A-D7E65E87C39F@adamw.org> References: <201705301415.v4UEFNJv049083@mech-as222.men.bris.ac.uk> To: mexas@bris.ac.uk X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>; List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 30 May 2017 14:30:34 -0000 > On 30 May, 2017, at 8:15, Anton Shterenlikht <mexas@bris.ac.uk> wrote: >=20 >> =46rom adamw@adamw.org Tue May 30 15:03:31 2017 >>=20 >> The ports tree continues to evolve. Major new features are planned = and in the process of being implemented. These changes will break all = the port-building tools. >=20 > oy vei >=20 >> poudriere and synth are actively developed, so they will quickly = support the new changes. portmaster and portupgrade are no longer being = actively developed, so it is anticipated that they will stop working = until somebody fixes them (if at all). >=20 > I last used poudriere a couple years back. > It is much more involved than portmaster > (obviously, these 2 tools are not doing the same job) There's definitely more work up-front to set up poudriere. You get the = effort back, though, in long-term viability and not having to chase = problems up and down the ports tree. >> So no, portmaster isn't going away. But, there's no guarantee that it = will keep working. We strongly, strongly advise everyone to use = poudriere or synth to build their ports, and then plain old "pkg = upgrade" to handle updates. >=20 > because my experience of poudriere was mixed, > I haven't used it at all on amd64. > pkg is great. And when occasionally I need > non-default options I use portmaster. >=20 >>=20 >> The vast majority of problems reported on this mailing list exist = only in portmaster/portupgrade, because they do not do clean builds. At = this point, portmaster should only be used by people with enough ports = development experience to understand and mitigate conflicts and various = build errors. >=20 > I agree that a dirty environement is mostly > the source of bad portmaster builds. >=20 > However, to create the whole poudriere enviroment > to build a port a week, or maybe a month, seems > like an overkill. >=20 > Yes, I know, it's a volunteer project, things > evolve, unless somebody steps in... >=20 > If my recollection of poudriere is correct, > I'll need a separate ports tree? > And if I only need to build a single port > with custom settings, I'll have to start > every time from scratch? > And if I want to use this single port with > default settings with my other ports, I need > to make sure the 2 port trees are in sync. >=20 > Sorry if I don't do poudeire justice, it's been a while... You don't need separate port trees. The idea is to use poudriere to = build ALL your ports. Just make a list of the ports you want, pass it to = poudriere, and it will keep everything up-to-date, rebuild things when = they need to be rebuilt, and give you a pkg repository so you can just = run "pkg install foo" or "pkg upgrade" to keep your system running. Even if you do use poudriere to build only a few ports, it's pretty = easy. Give your own generated packages a higher priority in = /usr/local/etc/pkg/repos/ and you can transparently layer your pkg repo = above the upstream repo. So no, you don't need separate ports trees. poudriere is happiest though = when you let it manage its own ports tree, so I prefer to just symlink = /usr/ports to it, but you can very easily use a pre-existing ports tree = with poudriere. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170530141321.6FEF912303A3>