From owner-freebsd-ports@freebsd.org Tue Sep 27 06:11:24 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 A2F1BBEB142 for ; Tue, 27 Sep 2016 06:11:24 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 69A0FD51 for ; Tue, 27 Sep 2016 06:11:24 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-ports@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bolbu-003bbi-19>; Tue, 27 Sep 2016 08:11:22 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-ports@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bolbt-001YE1-QU>; Tue, 27 Sep 2016 08:11:21 +0200 Date: Tue, 27 Sep 2016 08:11:21 +0200 From: "O. Hartmann" To: freebsd-ports Subject: Check constistency of the installed ports Message-ID: <20160927081121.5a78cd4c@freyja.zeit4.iv.bundesimmobilien.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 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, 27 Sep 2016 06:11:24 -0000 As a user of ports-mgmt/portmaster, I face very often the situation with this tool, that it fails in the very last stage of registering an installation or update of a port. So it happens to, for example, updates for print/tex-xetex and somehow (not being aware of) print/tex-luatex. Anyway, if someone skips the error messages produced by portmaster - like me by rerunning portmaster again - the installed ports are somehow inconsistent. Rerunning "portmaster texlive-full" reveals the obvious: ===>>> The following actions will be taken if you choose to proceed: Re-install texlive-full-20150521 Install print/tex-luatex Install print/tex-xetex I use "old-style" port building via compiler and and the sources in the ports tree. This is due to a lot of individual configurations and personal likes. I mention this avoiding people delegating me towards "pkg" for this task. The major question is: I sthere a way to check the consistency of the installed ports to reveal such gaps as shown above? Thank you very much in advance for the time taken to answer, please CC me, I do not subscribe the list. Kind regards, Oliver