Date: Wed, 11 Jun 2014 18:01:43 +0100 From: Matthew Seaman <matthew@freebsd.org> To: freebsd-ports@freebsd.org Subject: Re: What is the preferred method for updating ports now? Message-ID: <53988B77.1050407@freebsd.org> In-Reply-To: <C837118D8018025B681180B9@localhost> References: <C837118D8018025B681180B9@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53988B77.1050407>