Andre Goree an...@drenet.info writes:
I seem to have to run 'make index' in /usr/ports after I've run 'svn up
/usr/ports' in order to see which ports need to be updated using
'portversion'. This doesn't seem correct...and if so portsnap would
seem like a much better tool. Perhaps I should
On Sat, 30 Mar 2013 08:56:12 -0400, Lowell Gilbert
freebsd-questions-lo...@be-well.ilk.org wrote:
Andre Goree an...@drenet.info writes:
I seem to have to run 'make index' in /usr/ports after I've run 'svn up
/usr/ports' in order to see which ports need to be updated using
'portversion'.
On Fri, 29 Mar 2013 21:52:41 -0400, Damien Fleuriot m...@my.gd wrote:
On 29 March 2013 22:29, Andre Goree an...@drenet.info wrote:
I seem to have to run 'make index' in /usr/ports after I've run 'svn up
/usr/ports' in order to see which ports need to be updated using
'portversion'. This
I seem to have to run 'make index' in /usr/ports after I've run 'svn up
/usr/ports' in order to see which ports need to be updated using
'portversion'. This doesn't seem correct...and if so portsnap would
seem like a much better tool. Perhaps I should be running 'make
fetchindex' instead? I'm
On 29 March 2013 22:29, Andre Goree an...@drenet.info wrote:
I seem to have to run 'make index' in /usr/ports after I've run 'svn up
/usr/ports' in order to see which ports need to be updated using
'portversion'. This doesn't seem correct...and if so portsnap would
seem like a much better