From owner-freebsd-ports@freebsd.org Thu Dec 8 13:48:05 2016 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 EB9D6C6D276 for ; Thu, 8 Dec 2016 13:48:05 +0000 (UTC) (envelope-from Werner.Griessl@uni-bayreuth.de) Received: from btr0xn.rz.uni-bayreuth.de (btr0xn.rz.uni-bayreuth.de [132.180.8.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailhub-out.uni-bayreuth.de", Issuer "Universitaet Bayreuth CA (UNIBT-CA) G01" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 64D2D119E for ; Thu, 8 Dec 2016 13:48:05 +0000 (UTC) (envelope-from Werner.Griessl@uni-bayreuth.de) Received: from btr0xn-rx.rz.uni-bayreuth.de (localhost [127.0.0.1]) by btr0xn.rz.uni-bayreuth.de (8.13.1/8.13.1) with ESMTP id uB8CQF06027141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 8 Dec 2016 13:26:15 +0100 (MET) Received: from btruxs.rz.uni-bayreuth.de (btruxs [132.180.14.11]) by btr0xn-rx.rz.uni-bayreuth.de (8.13.1/8.13.1) with ESMTP id uB8CQCsV027125 for ; Thu, 8 Dec 2016 13:26:12 +0100 (MET) Reply-To: Werner.Griessl@uni-bayreuth.de Subject: Re: The ports collection has some serious issues References: <20161208121626.2fec0076@gumby.homeunix.com> To: freebsd-ports@freebsd.org From: Werner Griessl Organization: UNI Bayreuth ITS Message-ID: Date: Thu, 8 Dec 2016 13:26:12 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161208121626.2fec0076@gumby.homeunix.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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: Thu, 08 Dec 2016 13:48:06 -0000 On 12/08/16 13:16, RW via freebsd-ports wrote: > On Thu, 8 Dec 2016 05:16:24 +0000 > Daniil Berendeev wrote: > >> 1) portmaster is not nice for the user. >> If it comes over an error even in one little tiny port that is a >> dependency for something bigger , it will abort its work and leave all >> the other ports not updated. So, if you try to to do `portmaster -af`, >> you should not forget `-m DISABLE_VULNERABILITIES=yes` (we will return >> to this one later) and you must pray to God for not coming around a >> circular dependency or some port that would fail to deinstall its >> older version. You can't leave portmaster for a night to update all >> the needed ports and deal with broken ones in the morning, you need >> to cherry pick the broken ports and ignore them, and then try to deal >> with them. >> >> Although portmaster is not releated to the FreeBSD project and is an >> outside tool, there aren't any alternatives from the project itself. >> So use it or die. Not a nice situation. > > There's portupgrade. It doesn't stop on the first error but carries on > with ports that don't depend on any broken ports. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > I use portsnap in combination with portupgrade Werner -- Werner Grießl D-95440 Bayreuth, Germany Universitaet Bayreuth Tel.: +49 921 55 2685 IT-Servicezentrum/Netze NW2 3.2.U1.143