From owner-freebsd-ports@FreeBSD.ORG Wed Jun 11 17:41:51 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B176F5D2 for ; Wed, 11 Jun 2014 17:41:51 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FA352138 for ; Wed, 11 Jun 2014 17:41:50 +0000 (UTC) Received: from [192.168.0.100] ([87.139.233.65]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LdHLB-1WUYWy2MHx-00iWGj; Wed, 11 Jun 2014 19:41:41 +0200 Message-ID: <539894D6.5090304@gmx.de> Date: Wed, 11 Jun 2014 19:41:42 +0200 From: olli hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Paul Schmehl Subject: Re: What is the preferred method for updating ports now? References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ZwZSxZngbCg80QNHUmyvuSzu/AGJLd2b4dDiA2iKzTiFXN33eGk JjEWLZkudM6ysvYVpTtePoc/4pHJSgVNk7oqSMEoTniLJDhjhKZ9kz4RgxOI/Rht5iqooSp 1TcDT4X85YKk6fO9/nHO0XKUCS6c23eonlzucvo5+D8nzySzzaE3TMYrfih8zN5yeFvY+Jr RX4qh8AVZRN3UOAgKmSbA== Cc: FreeBSD Ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 17:41:51 -0000 On 2014-06-11 18:20, Paul Schmehl wrote: > I used to use cvsup. Then I switched to portsnap. Do I now need to switch to svn? Hi Paul, portsnap is fine and I haven't heard any rant it will go away. cvsup was a different part, with the switch to SVN every commit was also staged in the background to CVS to keep cvsup alive. Sice cvs was also removed from the base OS there was no longer a benefit to keep cvsup running. https://wiki.freebsd.org/CvsIsDeprecated > 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? simply go to the root of your portstree and fire the command `svn up', but watch the output for conflicts marked with a capital 'C'. Running from time to time `svn cleanup' will keep remove dead metadata from the .svn directory. In case you prefer portsnap for your tree and svn only for maintain your ports thats also fine. There is a way to do sparse svn checkouts (only ports you maintain) # sparse checkout $ cd $space $ svn checkout --depth empty $svn/url my_svn_workdir # checkout my ports $ cd my_svn_workdir # checkout all top $cat dirs with maintained port $ svn up --set-depth empty devel dns math net net-mgmt security sysutils www x11-toolkits # checkout maintained ports $ grep $my@maintainer.email /usr/ports/INDEX-8 | cut -d\| -f 2 | sed 's;/usr/ports/;;' | xargs svn up This way you can use portsnap for port building and svn to hack the ports you maintain. After your patches are committed simply use `svn up' in the workdir (also before you start hacking a port to limit conflicts) > 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...... Answered already by Matthew. -- HTH, olli