From owner-freebsd-questions@freebsd.org Tue Jun 30 17:01:34 2015 Return-Path: Delivered-To: freebsd-questions@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 AD4DA990670 for ; Tue, 30 Jun 2015 17:01:34 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from avasout08.plus.net (avasout08.plus.net [212.159.14.20]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 432531B3E for ; Tue, 30 Jun 2015 17:01:33 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk ([80.229.31.82]) by avasout08 with smtp id mh1U1q0031mJoLY01h1Vcv; Tue, 30 Jun 2015 18:01:30 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=EKD7qAtC c=1 sm=1 tr=0 a=cd0K7rcWwnZFf6xQxRobyA==:117 a=cd0K7rcWwnZFf6xQxRobyA==:17 a=D7rCoLxHAAAA:8 a=0Bzu9jTXAAAA:8 a=kj9zAlcOel0A:10 a=XAFQembCKUMA:10 a=NEAV23lmAAAA:8 a=CK6UTNwjaF2vVuJNMBoA:9 a=3M74Zzene2MW8pTv:21 a=6IUfLxNGekNcMIrK:21 a=CjuIK1q_8ugA:10 Received: from curlew.lan ([192.168.1.13]) by curlew.milibyte.co.uk with esmtp (Exim 4.85) (envelope-from ) id 1Z9yuV-0001ni-9h; Tue, 30 Jun 2015 18:01:28 +0100 Date: Tue, 30 Jun 2015 18:01:27 +0100 From: Mike Clarke To: Ewald Jenisch Cc: Message-ID: <20150630180127.30b5c124@curlew.lan> In-Reply-To: <20150630115303.GA1331@aurora.oekb.co.at> References: <20150630115303.GA1331@aurora.oekb.co.at> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; amd64-portbld-freebsd10.0) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Subject: Re: Mix'n'match between packages an ports? Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2015 17:01:34 -0000 On Tue, 30 Jun 2015 13:53:03 +0200 Ewald Jenisch wrote: > Here's my question: Is a "mix and match" between binary and > source-installation (pkg.. vs. "make / portupgrade") possible on the > same machine, or is it one or the other? It can be done, but with care. I currently have 2 ports which need building from source due to needing non-standard configuration and 2 more which aren't available as packages. As others have suggested poudriere is one way to go. I have tried this and it's certainly an excellent product but for my case, where only a very small number of ports required building from source, it was rather like using a sledgehammer to crack a nut. It's important that you keep your ports tree in step with the FreeBSD repositories and, as has already been said, it can be a bit more complicated now that the packages aren't built on a fixed schedule. The solution is to use Reed Cartwright's sync-ports script . This will obtain revision information from the relevant build server and use svnlite to update your ports tree to match the same version. My updating procedure is as follows: pkg lock -l # To check that the ports you build from source are # locked - lock them if not. sync-ports. make -C /usr/ports index pkg updating | less # To check for possible issues. pkg upgrade pkg version -vIL= # If any of your locally built ports need updating they will show up here # If one of your ports needs rebuilding run pkg unlock the_port_name portmaster the_port_name pkg lock the_port_name By upgrading packages before attempting to rebuild any ports you ensure that all dependencies will be up to date and you won't need to build any of them unless the new version has acquired any new dependencies since the last upgrade. The same procedure applies for ports which aren't available as packages, except that you don't need to bother about locking them. I've been using this procedure for over 3 months now and not had any problems. -- Mike Clarke