From owner-freebsd-ports@FreeBSD.ORG Wed Jun 11 17:02:04 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 72CBAB0E for ; Wed, 11 Jun 2014 17:02:04 +0000 (UTC) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "ca.infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AE132D4F for ; Wed, 11 Jun 2014 17:02:03 +0000 (UTC) Received: from ox-dell39.ox.adestra.com (no-reverse-dns.metronet-uk.com [85.199.232.226] (may be forged)) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.8/8.14.8) with ESMTP id s5BH1plS036892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 11 Jun 2014 18:01:56 +0100 (BST) (envelope-from matthew@freebsd.org) Authentication-Results: lucid-nonsense.infracaninophile.co.uk; dmarc=none header.from=freebsd.org DKIM-Filter: OpenDKIM Filter v2.8.3 smtp.infracaninophile.co.uk s5BH1plS036892 Authentication-Results: smtp.infracaninophile.co.uk/s5BH1plS036892; dkim=none reason="no signature"; dkim-adsp=none X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host no-reverse-dns.metronet-uk.com [85.199.232.226] (may be forged) claimed to be ox-dell39.ox.adestra.com Message-ID: <53988B77.1050407@freebsd.org> Date: Wed, 11 Jun 2014 18:01:43 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: What is the preferred method for updating ports now? References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ASON8w7tvuEArCp2egIMqswt748G0EfPl" X-Virus-Scanned: clamav-milter 0.98.3 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lucid-nonsense.infracaninophile.co.uk 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:02:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ASON8w7tvuEArCp2egIMqswt748G0EfPl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 06/11/14 17:20, Paul Schmehl wrote: > 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? To maintain a copy of the ports tree, portsnap is probably least effort, unless you're maintaining ports or want to make local customizations, in which case use svn. > Is portmaster going away any time soon? Or is that now the preferred > method for updating ports? Is portupgrade going away? (I no longer us= e > it - just wondering.) No. portmaster and portupgrade are here for the foreseeable future. There's no reason to stop using them if they are your tools of choice. Neither of those are specifically preferred for updating ports -- in fact, there isn't any one method that is "preferred": ports supports installing from source, with or without using tools like portmaster or portupgrade, and it now also supports installing using binary packages either from the FreeBSD official repositories or other repositories; either your own, or run by (hopefully reputable) third parties like PC-BSD for instance. > 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? >=20 > So many questions...... Yes, portlint is still important. However as a developer, you should add= DEVELOPER=3DYES to your /etc/make.conf -- this will enable a number of sanity tests now built into the ports Makefiles. This, plus the adoption of staging means that you should be able to do unit tests on an updated port as simply as: % make stage % make check-orphans % make package PACKAGES=3D/tmp which you can run as an ordinary user, rather than needing root level access (assuming you've installed all the dependencies already.) If your port passes all those, then it's in good shape, although I'd recommend further testing via Redports or the like before committing to the tree. Cheers, Matthew --ASON8w7tvuEArCp2egIMqswt748G0EfPl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJ8BAEBCgBmBQJTmIt+XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTn22IQAJqQf7yndxNZGu+Ou7gXL5KC nTK+TLEe6+E5Ut6lSmtpkCz/LHH2vHVlVPerFYzWOMeNSqeX/srLVpkmVAeRXKKn KaMWFzOy9Ft2O+ovFqxAXm4PEBu3h4ylv8omTjN4exeFAu2qQq9GH2w/l/mazxFt oCdGyo5/vVIAEp8zkS+7blkWqvYQRHY7dy22NDTtrX4Ug5Nb/b0LKuBoSI9rBNRq kNPQM2wPhEBOT5ggSHTfJ215YefLUWtIXqxGNBT9Uewqw/R350MTQDICLSD2pG21 AqAh32E+XOTPzWTyC6kgrscFJ+2IIKejMxxqwBc5LY9D+QPI7t2FX8HNJbEoUHfN nBS9ejkAIXJGfmLDzI+T6jOZycrCMpNE464We/5W0gucfNIKgZY+A5RDRKJ60iKc ExIjjWVWe0o4lDQcfSzr4iUq5ihkllsXb83jjutvKeQ3ee3EmSbT/5TeoN0GA0fF m0412m319Jcwb20zg39mC3ItDx7yAckdPUlyTPLLTNyV92BQo/TvRah+K9Mnqrfv 69G3s5NBz+2yBD6/FGtV26qy7+fBVRvaH9+ttjyBHgIJNgebHx8r7D3YEvei1Bk6 e8mCevNGPCM8X4W8ABClNfTzIyckImHWh2/Xea7Li0MhjkVfGUbF8V5G9rTsjLcU xeEUJQh9288EBQWCMqNM =Ku6i -----END PGP SIGNATURE----- --ASON8w7tvuEArCp2egIMqswt748G0EfPl--