From owner-freebsd-ports@freebsd.org Tue May 30 14:15:27 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 3241AB7E0D0 for ; Tue, 30 May 2017 14:15:27 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACCF238A9 for ; Tue, 30 May 2017 14:15:26 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: by mail-wm0-x243.google.com with SMTP id d127so25497618wmf.1 for ; Tue, 30 May 2017 07:15:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bris-ac-uk.20150623.gappssmtp.com; s=20150623; h=date:from:message-id:to:subject:cc:reply-to:in-reply-to; bh=OTcUtIKgBRP+pBYih8On3bAZQhrCaL1/crwC80TSlP0=; b=NVNBavEwjYb3sQTyUCLF9OeDT2H0lOBYtEX1LiiVg6nLWnoFnzxMTdTzOUVFOfwAcY eSfz8ZskAYl8f9RE3TOFRLxIt6D4y50WfsRNHv1M3BTBfPpCGZoI4AKb2a3Pu+vVkBIp 5nlo+QGyJXARM9RYKqXhf+saWUsKqTT/KkaePzG9zBhrkoRGG9efeFDiYOCtXdtdfsKq kfirDdUQP6Umblh/z7YuMhBnsj/b+lbnDyFJgROF9/dtucyJUZ6Pq2nmlhISilRCCdjF xOKNpVYNrWB8RID6lJT5vms14HDD73Yd8LS5jrtvetIjQ3GEDwxow1nCLq2q3Mt8WnDP 1DZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:message-id:to:subject:cc:reply-to :in-reply-to; bh=OTcUtIKgBRP+pBYih8On3bAZQhrCaL1/crwC80TSlP0=; b=F4LIxTdnFt63kUP47CivJxmP/s6+2o0pik2z9ie99iF9j8A0H6ivvHlL18tITvTqeU qqJ3eF4mtoEz/oITx6NPFKsEF3MXe7o4qqbLJUvqRuZp7sc76yGHhapaet8onQdiqDZ/ JcT0lvoHXalcRJt0sTrRmkjG6NX5+pQn0ZUNjOLRlHIu+lYcZhLz/I70jPrw26H9Dhlx /8BYrrwbJONls1tdhFWkLSCjv/ZNTRBESOfgE55VJnzDWQdyD6XYz4q+I7os7lEKLwyf /wqWPdIZyrOzbtn5GGJ9vQpvwG4stIWDexAh/BrOaTkJGXD8W+HHbJf6deMPfWQnXEZ9 xAmg== X-Gm-Message-State: AODbwcD+DGr7wog7Uv15jNL3H74q1+4g4kf00B8+4vK0XnCvgAS4uoMo JOm6yEaVnh8Rbq5a X-Received: by 10.28.57.9 with SMTP id g9mr1843156wma.120.1496153725057; Tue, 30 May 2017 07:15:25 -0700 (PDT) Received: from mech-as222.men.bris.ac.uk (mech-as222.men.bris.ac.uk. [137.222.170.4]) by smtp.gmail.com with ESMTPSA id y6sm16088794wrc.51.2017.05.30.07.15.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 May 2017 07:15:24 -0700 (PDT) Received: from mech-as222.men.bris.ac.uk (localhost [127.0.0.1]) by mech-as222.men.bris.ac.uk (8.15.2/8.15.2) with ESMTP id v4UEFNbN049084; Tue, 30 May 2017 15:15:23 +0100 (BST) (envelope-from mexas@mech-as222.men.bris.ac.uk) Received: (from mexas@localhost) by mech-as222.men.bris.ac.uk (8.15.2/8.15.2/Submit) id v4UEFNJv049083; Tue, 30 May 2017 15:15:23 +0100 (BST) (envelope-from mexas) Date: Tue, 30 May 2017 15:15:23 +0100 (BST) From: Anton Shterenlikht Message-Id: <201705301415.v4UEFNJv049083@mech-as222.men.bris.ac.uk> To: adamw@adamw.org, mexas@bris.ac.uk Subject: Re: The future of portmaster Cc: freebsd-ports@freebsd.org, rollingbits@gmail.com Reply-To: mexas@bris.ac.uk In-Reply-To: <9FEDBFCE-27D1-432B-926B-7BF401AD7B19@adamw.org> 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: Tue, 30 May 2017 14:15:27 -0000 >From adamw@adamw.org Tue May 30 15:03:31 2017 > >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. oy vei >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). 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) >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. 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. > >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. I agree that a dirty environement is mostly the source of bad portmaster builds. However, to create the whole poudriere enviroment to build a port a week, or maybe a month, seems like an overkill. Yes, I know, it's a volunteer project, things evolve, unless somebody steps in... 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. Sorry if I don't do poudeire justice, it's been a while... Anton