Ports question ....

Roland Smith rsmith at xs4all.nl
Fri Aug 29 21:11:51 UTC 2014


On Fri, Aug 29, 2014 at 07:00:23AM -0500, William A. Mahaffey III wrote:
> 
> On 08/28/14 17:51, Roland Smith wrote:
> > On Thu, Aug 28, 2014 at 02:43:49PM -0500, William A. Mahaffey III wrote:
> >>
> >> .... How do I check to see if the ports collection has been updated ? I
> >> had some problems a week or so ago getting some stuff to compile. There
> >> were some later posts alluding to some ports being a bit stale .... If
> >> that was my problem, I'd like to update & try again ....
> > The http://www.freshports.org/ site gives a nice overview of recent port
> > changes. It also lists the SVN revision. If you use subversion to keep your
> > ports tree up to date you can check the state of your ports tree with;
> >
> >      > svnlite log -r HEAD /usr/ports/
> >      ------------------------------------------------------------------------
> >      r366459 | danilo | 2014-08-29 00:34:41 +0200 (Fri, 29 Aug 2014) | 2 lines
> >
> >      - Update from 1.40.01 to 1.40.02
> >
> >      ------------------------------------------------------------------------
> >
> > In this case my ports tree is at r366459.
> >
> > Generally I like to update my ports tree weekly. That *generally* makes for
> > relatively small updates using svnlite (in the base system in FreeBSD 10) and
> > ports-mgmt/portmaster;
> >
> >      # svnlite /usr/ports
> >      # less /usr/ports/UPDATING
> >      # portmaster -ai
> >
> > Reading UPDATING is important! Sometimes updates need special actions.
>
> This sounds like it is very close to what I am looking for. I typed in 
> the above command & the shell said command not found .... What pkg('s) 
> do I need for svnlite support ? TIA ....

Svnlite is in the base system in FreeBSD 10. You can use the devel/subversion
port instead. The executable is called “svn”.

Currently you can also use portsnap (which is also in the base system in
FreeBSD 10) to update the ports tree. But it is vulnerable to
man-in-the-middle attacks.[1] Unless someone steps up to fix this, one of the
possible scenarios is to retire portsnap once svnlite is in all supported
releases.

[1]: http://lists.freebsd.org/pipermail/freebsd-questions/2014-April/257394.html

Roland
-- 
R.F.Smith                                   http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 5753 3324 1661 B0FE 8D93  FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20140829/d590392c/attachment.sig>


More information about the freebsd-questions mailing list