From owner-freebsd-ports@FreeBSD.ORG Wed Jun 11 16:22:55 2014 Return-Path: <owner-freebsd-ports@FreeBSD.ORG> Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0002CE9E for <freebsd-ports@freebsd.org>; Wed, 11 Jun 2014 16:22:54 +0000 (UTC) Received: from ip-001.utdallas.edu (ip-001.utdallas.edu [129.110.180.40]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtpauth.utdallas.edu", Issuer "COMODO High-Assurance Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A4A329A9 for <freebsd-ports@freebsd.org>; Wed, 11 Jun 2014 16:22:53 +0000 (UTC) X-Group: None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Au0FAH6BmFOBbgogVWdsb2JhbABarxcBAQEBAQEBAQYKhEGVbQQBFwQHAgkHFCiEQgKBYxqIVaEghxyPBZhAF4VcjC+BFgSKOacaHw X-IPAS-Result: Au0FAH6BmFOBbgogVWdsb2JhbABarxcBAQEBAQEBAQYKhEGVbQQBFwQHAgkHFCiEQgKBYxqIVaEghxyPBZhAF4VcjC+BFgSKOacaHw X-IronPort-AV: E=Sophos;i="5.01,459,1400043600"; d="scan'208";a="18257982" Received: from zxtm01.utdallas.edu (HELO utd71538.utdallas.edu) ([129.110.10.32]) by ip-001.utdallas.edu with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Jun 2014 11:20:59 -0500 Date: Wed, 11 Jun 2014 11:20:44 -0500 From: Paul Schmehl <pschmehl_lists@tx.rr.com> Reply-To: Paul Schmehl <pschmehl_lists@tx.rr.com> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: What is the preferred method for updating ports now? Message-ID: <C837118D8018025B681180B9@localhost> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=1207 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 11 Jun 2014 16:22:55 -0000 I used to use cvsup. Then I switched to portsnap. Do I now need to switch to svn? If so, is there a way to use svn to only update those ports that have changed since the last update? I've been using svn for a while to work on port updates. I know how to fetch the entire port infrastructure but not how to only update those ports that have changed. Portsnap can be automated to keep ports up to date. Is there a similar utility that uses svn instead? Is portmaster going away any time soon? Or is that now the preferred method for updating ports? Is portupgrade going away? (I no longer use it - just wondering.) As a port maintainer, what tools do I use now that I've converted to pkgng? Do we still use portlint? Or is there a new way to do that? So many questions...... -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell