On Sat, Aug 03, 2013 at 03:17:02PM -0700, Steve Kargl wrote: > > The port was at 1.8.x before I added the additional lookup of > > svnlite to the script. > > My installed port was at 1.7.9. I can't find anywhere that > states that one must immediately upgrade to a new version > when a port's maintainer updates it. I've banged my head > against the ports collection dependency idiocy too often > to chase after every update. > Fair enough. > > There really is no need for UPDATING entry, since 1.7.9 is > > deprecated, and the behavior you have seen is not a fatal > > error with the buildkernel process. > > Installing a freshly built kernel when an ERROR message appears > within the last 10 lines of 'make buildkernel' seems like a > rather dumb thing do. > But the last 3 lines state that the kernel build completed. > > BTW, you should upgrade devel/subversion anyway, since there are > > security vulnerabilities. > > 1.7.9 works/worked fine for updating my /usr/src and my personal > svn repository. The change to use svnlite in newvers.sh should > have an entry in UPDATING to alert users that have a too old > svn port that they need to upgrade. I go as far to suggest that > that the script should look for svn in the path before it looks > for svnlite. I cannot differentiate what version of svn is used to check out the tree. When in doubt, software in base wins, IMHO. Glen
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:40 UTC