Date: Wed, 12 Sep 2018 09:00:03 +0000 From: Lorenzo Salvadore <phascolarctos@protonmail.ch> To: FreeBSD Ports <freebsd-ports@freebsd.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DSSspBUBo_aSQ_bGi8_CBV9IdO1j17kuYe-jVNqIY4ClYklg74cicw2TEpzrGs16p4-mfmQ6fQL9avj9EVd1Sq9dMiLndB97a6NpOUO9hg4=>