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
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Reply via email to