From owner-freebsd-ports@freebsd.org  Wed Sep 12 09:00:14 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E06D8108CA4E
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Wed, 12 Sep 2018 09:00:14 +0000 (UTC)
 (envelope-from phascolarctos@protonmail.ch)
Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch
 [185.70.40.132])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.protonmail.ch",
 Issuer "QuoVadis Global SSL ICA G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 77EC87982F
 for <freebsd-ports@freebsd.org>; Wed, 12 Sep 2018 09:00:14 +0000 (UTC)
 (envelope-from phascolarctos@protonmail.ch)
Date: Wed, 12 Sep 2018 09:00:03 +0000
To: FreeBSD Ports <freebsd-ports@freebsd.org>
From: Lorenzo Salvadore <phascolarctos@protonmail.ch>
Reply-To: Lorenzo Salvadore <phascolarctos@protonmail.ch>
Subject: Re: how to enforce one version of python
Message-ID: <DSSspBUBo_aSQ_bGi8_CBV9IdO1j17kuYe-jVNqIY4ClYklg74cicw2TEpzrGs16p4-mfmQ6fQL9avj9EVd1Sq9dMiLndB97a6NpOUO9hg4=@protonmail.ch>
In-Reply-To: <c8d8c8be-caac-f49e-0ec1-b9b08a34218f@zyxst.net>
References: <fcb50bfe-c21f-a3ba-9d9f-2af92c3565d4@zyxst.net>
 <20180911145151.zgyeaiobnvkuo2rg@ivaldir.net>
 <4cd79546-c301-4ab7-13eb-3233736953f5@yandex.ru>
 <c8d8c8be-caac-f49e-0ec1-b9b08a34218f@zyxst.net>
Feedback-ID: X6az_D2smWSR8MT5MHqXnWF0upxehDyHia7Id1cbayHNBUkRu3CIeusDsZHiivIIjmaKB1_OofpALrRUYjNz3w==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-1.1 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no
 version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.protonmail.ch
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.27
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: Wed, 12 Sep 2018 09:00:15 -0000

> Maybe I need to stop using portupgrade. What is the best replacement?

I never liked traditional updaters: to me, they seem too complex for a task=
 that
should be rather simple. Thus I wrote one myself: Caronte.
It has not yet been committed to the port tree, but you can find the port
here, waiting for a commit:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230769

Keep in mind that the project is new and I have not tested it in many
situation yet. In particular, I found that I need to work a bit in the
case new options are added to a port after an update (at the moment,
in this case, the upgrade is suspended in the configuration step of the
updated port until you press CTRL + C), but I will fix that as soon as
possible (it was not a priority until I was the only user).

I think my updater has a nice behavior with flavors (read manpage),
but if it has not, you can post an issue on github and I will deal with it
as a priority:

https://github.com/lsalvadore/caronte

Lorenzo Salvadore.